A Spec Kit extension that derives four stakeholder-facing artifacts from a technical spec.md and plan.md. Output follows Amazon Working Backwards (PRFAQ), Jobs to Be Done (Ulwick), Gherkin BDD, and Lean PRD conventions, in plain language, with a strict no em dash style. The artifacts follow the language of your spec, so a spec in Chinese, Spanish, or Arabic gives artifacts in that language.
The full guide lives in the project wiki. This README is the front door only.
| Wiki page | When to read |
|---|---|
| Home | Overview and reading order. |
| Getting Started | First install, zero to first generated artifact in five minutes. |
| Commands | Deep reference for the three /speckit.product.* commands. |
| Workflow | Input and output flow, recommended order, the product/ layout. |
| Examples | Sample spec.md input and the four artifacts it produces. |
| Style Guide | The voice rules every generated artifact enforces. |
| Diagrams | How diagrams and optional sections are generated, and the value gate. |
| Troubleshooting | Error codes, refusals, common breakages and their fixes. |
| FAQ | Conceptual questions and design rationale. |
| Architecture | How the extension works when you run a command. |
The wiki is generated from docs/ on every push to main. To browse the same content as plain markdown, open the docs folder.
This README uses the slash-command names, such as /speckit.product.brief. Skills agents, such as Claude Code, use hyphens instead: /speckit-product-brief.
| Command | Reads | Writes | Audience |
|---|---|---|---|
/speckit.product.brief |
spec.md |
product/00-info.md, product/10-spec.md |
Any stakeholder, PMs, leadership |
/speckit.product.plan |
plan.md, spec.md |
product/20-plan.md |
PMs, engineering leads |
/speckit.product.design |
plan.md, spec.md, optional more |
product/30-design.md |
Tech leads, senior developers |
All three commands also update their section of the shared product/checklist.md (/speckit.product.brief writes both the Info and Spec sections). No command modifies spec.md or plan.md.
Spec Kit offers each command as an optional hook. After /speckit.specify and /speckit.clarify it offers /speckit.product.brief. After /speckit.plan it offers /speckit.product.plan, then /speckit.product.design.
spec.md and plan.md are canonical. Everything under product/ is a derived view, regenerated on demand by rerunning the matching command and choosing overwrite. [NEEDS CLARIFICATION] markers in spec.md are surfaced as open product questions in the generated output, never silently resolved.
Requires Spec Kit >= 0.12.17 initialized in the project (specify init).
Install directly from the latest release:
specify extension add product --from https://github.com/d0whc3r/spec-kit-product/releases/download/v2.2.0/product-2.2.0.zipChange the version in the URL to pin a different release. To update, run the same command with a newer release URL and add --force.
Spec Kit lists the extension in its community catalog. Run specify extension search product or specify extension info product to see the entry. That catalog is discovery only, so install by name (specify extension add product) does not work. See Troubleshooting.
For prerequisites and the first-run walkthrough see Getting Started.
See CONTRIBUTING.md at the repo root.
MIT. See LICENSE.