A Spec Kit extension

Turn your engineering spec into product artifacts stakeholders actually read.

Product Spec Extension reads the spec.md and plan.md you already have and generates four audience-specific documents: a stakeholder summary, a full product spec, a delivery plan, and a technical design. Each one ships with a quality checklist. Your source files are never modified.

Install with Spec Kit

specify extension add product

Get started Read the docs

4 commands
Requires Spec Kit >= 0.2.0
MIT licensed
No em dashes, plain English

Why this exists

spec.md is written for engineers. Product managers, leadership, designers, and cross-functional reviewers need the same information in a different shape. Rewriting that by hand for every feature is busywork and drifts from the canonical spec. This extension generates the audience-specific views for you, from the spec you already wrote.

Source stays canonical

spec.md and plan.md are read-only to the extension. Every artifact lands under product/ in the same feature directory. Regenerate any time the source changes.

Built-in quality checklist

Every command updates a shared checklist.md. A failed Required item is your signal to regenerate, so the output stays trustworthy.

Proven conventions

Output follows Working Backwards (PRFAQ), Jobs to Be Done, Gherkin BDD, and Lean PRD conventions, in plain English with a strict no em dash style.

The four commands

Each command stands alone and reads from a feature directory under specs/. Stop at the level of detail your audience needs.

Command	Reads	Writes	Audience
`/speckit.product.info`	`spec.md`	`product/00-info.md`	Any stakeholder, non-technical
`/speckit.product.spec`	`spec.md`	`product/10-spec.md`	Product managers, 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 four also update the shared product/checklist.md. None of them modify spec.md, plan.md, or any other source file. Pass --feature-dir specs/<dir> to target a specific feature instead of the active one.

Get started in five minutes

Install the extension

The recommended install resolves the latest release:

specify extension add product

To pin a specific version:

specify extension add product --from \
  https://github.com/d0whc3r/spec-kit-product/releases/download/v0.5.2/product-0.5.2.zip

Create a feature

Run the Spec Kit core command and fill in the generated spec.md. The product commands refuse to run on an unfilled spec.
```
/speckit.specify
```
Generate your first artifact

Run the lightest command first to validate direction. It writes product/00-info.md and product/checklist.md.
```
/speckit.product.info
```
Generate the full set

Once direction is confirmed, generate the spec. After you have a Spec Kit plan.md (run /speckit.plan), add the plan and design views.
```
/speckit.product.spec
/speckit.product.plan
/speckit.product.design
```

How it flows

Input flows from the Spec Kit core commands into this extension. No two commands write to the same output file.

Spec Kit core               This extension
---------------             -----------------------------------------------

/speckit.specify --> spec.md --> /speckit.product.info   -> product/00-info.md
                            \--> /speckit.product.spec   -> product/10-spec.md

/speckit.plan --> plan.md --> /speckit.product.plan      -> product/20-plan.md
                        \---> /speckit.product.design    -> product/30-design.md

All four also write to:    product/checklist.md

The product/ folder is self-contained. Zip it, attach it to a doc, paste it into a slide deck. No engineering scaffolding needs to travel with it.

Frequently asked questions

Do I have to run all four commands?

No. Stop at the level of detail your audience needs. A small change that needs only stakeholder buy-in is just /speckit.product.info. A full feature definition is info plus spec. A feature in active build adds plan and design.

Will it modify my spec.md or plan.md?

No. The source files are read-only to this extension. Every artifact lives under product/ in the same feature directory. This is enforced by the command body and the constitution.

What happens to [NEEDS CLARIFICATION] markers in spec.md?

They are surfaced in the generated output as open product questions, never silently resolved. The relevant artifact lists them under a "Key Decisions" or "Risks and Open Product Questions" section.

Does the extension run by itself?

No. The commands are Markdown prompts. They need a Spec Kit-aware assistant to resolve and execute them. The release zip is portable and has no runtime of its own.

How do I upgrade the extension?

Run specify extension upgrade product. The CLI fetches the latest catalog entry and replaces the installed copy. Your generated product/*.md files are not touched.

Does this work in a brownfield codebase?

Yes. The bundled brownfield extension helps reverse-engineer specs from existing code. Once you have a spec.md, the product commands work the same way.