strategize

Name: strategize
Author: ghaida

519installs8forks

How to install strategize?

ghaida/intent/strategize

$npx -y skills add ghaida/intent --skill strategize

Installs into the current project.

Summary

Frames product design problems before solutions exist. Synthesizes research, sizes opportunities, defines hypotheses, scopes projects, and maps customer journeys. Use this skill for new project kickoffs, ambiguous business asks, translating research into briefs, strategic framing

Files · 1

View on GitHub

SKILL.md

1	# Strategize — Frame the Problem
2
3	## Overview
4
5	This skill owns the earliest, most critical phase of product design: problem framing. Before sketches, flows, or specs exist, it synthesizes evidence, identifies gaps, sizes opportunities, and establishes the conceptual foundation that guides all downstream work. This skill turns ambiguity into clarity through research synthesis, customer journey mapping, competitive analysis, and structured hypothesis definition.
6
7	When to activate this skill: New projects, fuzzy business requirements, research that needs translating into briefs, strategic pivots, stakeholder misalignment, unclear scope, opportunity validation, or competitive positioning work.
8
9	---
10
11	## Skill family
12
13	This skill works alongside the full Intent skill system:
14
15	- `/blueprint`: Once strategy is set, `/blueprint` maps how services, processes, and dependencies connect to produce outcomes. Engage when: creating service blueprints, mapping dependencies, analyzing failure modes, or designing the structural architecture behind an experience.
16	- `/journey`: After strategic framing, `/journey` structures the user experience — flows, task analysis, interaction sequences. Engage when: detailing specific user flows, creating wireflows, or designing step-by-step navigation.
17	- `/specify`: At the end of strategic and design work, `/specify` translates decisions into actionable briefs for development and other teams. Engage when: preparing design specs, writing technical handoff docs, or creating implementation guides.
18	- `/investigate` (Research): When the five foundational questions reveal knowledge gaps, `/investigate` plans and guides primary research — interview scripts, usability tests, surveys, diary studies. They execute the research; you synthesize findings back into the strategic frame.
19	- `/organize` (Information Architecture): After strategic framing, `/organize` structures the information space — taxonomies, navigation models, content hierarchies. Engage when: the solution fit question reveals complex information structures.
20	- `/articulate` (Content Strategy): Partners on messaging, voice, and content decisions that emerge from audience definition and competitive positioning. Engage when: strategic framing reveals that content is a core part of the value proposition.
21	- `/evaluate` (UX Assessment): Once strategy is set and design work begins, `/evaluate` provides structured UX assessment against heuristics and the Intent anti-pattern catalog. Engage when: validating that design execution aligns with strategic intent.
22	- `/measure` (Metrics & Success): Partners on defining success metrics tied to your hypotheses. Each foundational question should connect to measurable outcomes. Engage when: you need to quantify strategic goals or define what "working" looks like.
23
24	- `/philosopher`: A cross-cutting cognitive mode — not a phase — that any skill can enter when the problem needs more exploration before the next move. Invoke when: a brief feels too tidy, the five foundational questions return obvious answers, you suspect you're asking the wrong questions, or the user says "sit with this", "brainstorm", "I'm stuck", or "what am I missing." The philosopher helps reframe assumptions, find the problem adjacent to the stated problem, and challenge whether the opportunity is where everyone thinks it is.
25
26	Note on visual design: Visual identity and design systems live outside this skill system. The Strategist establishes strategic context that informs visual direction, but the visual design work itself is a separate discipline.
27
28	Route intelligently: If a user wants to understand how a system works structurally — the services, dependencies, and processes behind an experience — suggest `/blueprint`. If they want to map the user-facing sequence and interaction, suggest `/journey`. If they need to plan or conduct user research, suggest `/investigate`. If they want to structure information and navigation, suggest `/organize`. If they want to define content strategy and voice, suggest `/articulate`. If they want to assess design quality, suggest `/evaluate`. If they want to define success metrics, suggest `/measure`. If they want to communicate decisions downstream, suggest `/specify`. If the problem itself feels underexplored, the framing feels shallow, or the user wants to sit with the problem before moving forward — enter `/philosopher` mode.
29
30	---

People who liked this also viewed

6 picks

Type

strategize

519installs8forks

View on GitHub

How to install strategize?

ghaida/intent/strategize

$npx -y skills add ghaida/intent --skill strategize

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Strategize — Frame the Problem
2
3	## Overview
4
5	This skill owns the earliest, most critical phase of product design: problem framing. Before sketches, flows, or specs exist, it synthesizes evidence, identifies gaps, sizes opportunities, and establishes the conceptual foundation that guides all downstream work. This skill turns ambiguity into clarity through research synthesis, customer journey mapping, competitive analysis, and structured hypothesis definition.
6
7	When to activate this skill: New projects, fuzzy business requirements, research that needs translating into briefs, strategic pivots, stakeholder misalignment, unclear scope, opportunity validation, or competitive positioning work.
8
9	---
10
11	## Skill family
12
13	This skill works alongside the full Intent skill system:
14
15	- `/blueprint`: Once strategy is set, `/blueprint` maps how services, processes, and dependencies connect to produce outcomes. Engage when: creating service blueprints, mapping dependencies, analyzing failure modes, or designing the structural architecture behind an experience.
16	- `/journey`: After strategic framing, `/journey` structures the user experience — flows, task analysis, interaction sequences. Engage when: detailing specific user flows, creating wireflows, or designing step-by-step navigation.
17	- `/specify`: At the end of strategic and design work, `/specify` translates decisions into actionable briefs for development and other teams. Engage when: preparing design specs, writing technical handoff docs, or creating implementation guides.
18	- `/investigate` (Research): When the five foundational questions reveal knowledge gaps, `/investigate` plans and guides primary research — interview scripts, usability tests, surveys, diary studies. They execute the research; you synthesize findings back into the strategic frame.
19	- `/organize` (Information Architecture): After strategic framing, `/organize` structures the information space — taxonomies, navigation models, content hierarchies. Engage when: the solution fit question reveals complex information structures.
20	- `/articulate` (Content Strategy): Partners on messaging, voice, and content decisions that emerge from audience definition and competitive positioning. Engage when: strategic framing reveals that content is a core part of the value proposition.
21	- `/evaluate` (UX Assessment): Once strategy is set and design work begins, `/evaluate` provides structured UX assessment against heuristics and the Intent anti-pattern catalog. Engage when: validating that design execution aligns with strategic intent.
22	- `/measure` (Metrics & Success): Partners on defining success metrics tied to your hypotheses. Each foundational question should connect to measurable outcomes. Engage when: you need to quantify strategic goals or define what "working" looks like.
23
24	- `/philosopher`: A cross-cutting cognitive mode — not a phase — that any skill can enter when the problem needs more exploration before the next move. Invoke when: a brief feels too tidy, the five foundational questions return obvious answers, you suspect you're asking the wrong questions, or the user says "sit with this", "brainstorm", "I'm stuck", or "what am I missing." The philosopher helps reframe assumptions, find the problem adjacent to the stated problem, and challenge whether the opportunity is where everyone thinks it is.
25
26	Note on visual design: Visual identity and design systems live outside this skill system. The Strategist establishes strategic context that informs visual direction, but the visual design work itself is a separate discipline.
27
28	Route intelligently: If a user wants to understand how a system works structurally — the services, dependencies, and processes behind an experience — suggest `/blueprint`. If they want to map the user-facing sequence and interaction, suggest `/journey`. If they need to plan or conduct user research, suggest `/investigate`. If they want to structure information and navigation, suggest `/organize`. If they want to define content strategy and voice, suggest `/articulate`. If they want to assess design quality, suggest `/evaluate`. If they want to define success metrics, suggest `/measure`. If they want to communicate decisions downstream, suggest `/specify`. If the problem itself feels underexplored, the framing feels shallow, or the user wants to sit with the problem before moving forward — enter `/philosopher` mode.
29
30	---

People who liked this also viewed

6 picks

Type