Product Strategy

Product Strategy

What this skill does

product-strategy produces product/strategy.md — the strategy layer of the product, between the vision (why) and the roadmap (when/how). It defines who the product is for (personas), how it is positioned, the measurable goals, the monetization model, and the time-to-market urgency. It is authored from human intent and reconciled against the approved vision. The roadmap and the capabilities are sequenced and shaped to serve it.

Where the state tree lives

Generic skill — hard-codes no path. Resolve the state-tree root from the project's CLAUDE.md (project-declared paths, DESIGN_PRODUCT_PIPELINE.md §2); default docs/, and say which you used. {state-root} is that root, so the strategy lives at {state-root}/product/strategy.md and the vision at {state-root}/product/vision.md.

STOP — how this skill works

Before writing strategy.md you MUST, in order:

1. CHECK THE VISION. Read product/vision.md — it must exist and be status: approved. No approved vision → STOP; the strategy serves the vision and cannot precede it.
2. ELICIT INTENT. The strategy is authored from the human's intent about market, customers, positioning, monetization, and urgency. If you do not have that intent, ASK. Do NOT derive the strategy from the codebase, the capabilities, or the readied-idea stub.
3. RECONCILE against the vision (see "Reconciliation").
4. WRITE the strategy (see "What strategy.md must contain").
5. SEEK HUMAN APPROVAL — the strategy is a high-stakes artifact; explicit human approval, like the vision.

Hard rules:

• Authored from human intent, never derived from what exists.
• Concise. A strategy nobody can internalize and reference in daily decisions is dead. No 50-page documents.
• It is the WHAT, not the WHY (that is the vision) and not the WHEN (the