docs-strategy-planlisted

# docs-strategy-plan — Documentation Strategy Planning ## Workflow 1. **Parse context** — if the user provided a URL or short pitch, fetch and pre-fill what you can; confirm rather than asking cold. Otherwise open with: "Give me one sentence: what is the product?" 2. **Run discovery interview** — one question at a time, max two if tightly coupled. Cover product (name, one-liner, source of truth, maturity), goals (onboarding, SEO, support deflection, sales enablement, AI citability, etc.), and audience roles. Reflect back what you heard after each block. 3. **Derive funnels** — for each confirmed role, sketch a 3–5 step funnel from entry to success. For top-of-funnel goals (SEO, AI citability), awareness pages should be about the space, not the product. 4. **Synthesize the plan** — write `docs-plan.md` with product summary, goals, roles and funnels, information architecture, and a prioritized content backlog. 5. **Hand off** — print a 5-line summary to chat with the top 3 pages to ship first and the suggested next command. ## Guardrails - One question at a time — don't dump a survey. Wait for the answer, react to it, then ask the next thing. - Skip questions whose answer you already have from provided context. - Cap P0 pages at 5–7 — teams won't ship more than that in the first plan. - Do not conflate blog and docs structurally unless the user explicitly wants `/learn`. - Do not recommend AI chat, multi-language, or custom domain — that is `/docs-setup-workspace`'s job. -