SpecKit PRD
Create or update three consistent Markdown artifacts: a lean PRD for WHAT and
WHY, a technical roadmap whose SPEC catalog maps 1:1 to PRD Features, and a
roadmap-MOC that makes the spec tree navigable.
Ground recommendations
Inspect the tools and skills actually available. Follow the shared
capability-discovery
and grounding contracts. Read
applicable project instructions, .specify/memory/constitution.md, prior
roadmaps and decisions, and targeted code. Disclose uncertainty; do not guess.
Codex Skill-Selection Guard
If Codex loaded this Claude variant, stop and follow
../../codex-skills/speckit-prd/SKILL.md
as the active skill. The payload builder removes this guard from Claude installs.
Claude interaction adapter
In an active user chat, call AskUserQuestion for one question at a time. Each
call offers 2-3 mutually exclusive choices: put the grounded recommendation
first, suffix its label (Recommended), and state each tradeoff briefly. Wait
for the reply before the next question.
If no live user can answer because the skill was invoked in a background,
automation, CI, or subagent context, do not fabricate intent. A caller that
explicitly requested a draft may receive only a best-effort PRD from supplied
material, with every unvalidated decision in Open Questions and a clear
"interactive pass required" status. Do not claim the PRD is roadmap-ready and
do not create or update its roadmap or roadmap-MOC.
Workflow
Read and follow the shared PRD authoring protocol
before authoring. Determine whether the user is creating from an idea or updating
an existing PRD; before overwriting, confirm the exact output path and preserve
stable feature and SPEC identifiers for unchanged work. Use the shared
PRD template,
technical-roadmap template,
slicing heuristics, and, for
a new roadmap, roadmap-MOC template.
If docs/ai/specs/ubiquitous-language.md exists, read it first and use its
terms verbatim in the PRD. Apply the protocol's interview, update,
slicing/estimation, MOC, index, and verification rules. Report created or updated paths and recommend
/speckit-pro:speckit-scaffold-spec <SPEC-ID> for the first ready entry.
Output contract
docs/prd-<slug>.md: lean PRD with Problem, Goals, Non-goals, Features and
acceptance criteria, Migration or sequence when applicable, Module and
Interface Deltas (required; "No module or interface changes." is an explicit
valid entry), Constraints, Open Questions, and the 1:1 SPEC Catalog Crosswalk.docs/ai/specs/<slug>-technical-roadmap.md: ordered SPEC catalog with Source
PRD, scope, dependencies, status, reviewability budget, module and interface
deltas, key surfaces, and a reciprocal roadmap-MOC link.docs/ai/specs/<slug>-roadmap-MOC.md: curated epics plus the generator-owned
GENERATED:INDEX zone and a relative up: link to the roadmap.
This skill does not scope an existing roadmap entry (/speckit-pro:grill-me),
prepare a worktree or workflow (/speckit-pro:speckit-scaffold-spec), or teach
SDD methodology (/speckit-pro:speckit-coach). If the PRD already exists and
the user wants only a new roadmap, hand off to the Coach roadmap workflow.
1---2name: speckit-prd3description: Collaboratively create or update a lean PRD, its 1:1 technical-roadmap SPEC catalog, and a roadmap-MOC home note. Use when an active user asks to write a PRD, create a product requirements document, turn an idea or brief into a PRD and roadmap, plan a product, or invokes /speckit-pro:speckit-prd. Read-only workflow status and next-spec recommendations belong to /speckit-pro:speckit-status. Roadmap-only decomposition or dependency planning from an existing PRD, without creating or updating the PRD, belongs to /speckit-pro:speckit-coach. Ask one grounded decision at a time, then hand off the resulting roadmap to /speckit-pro:speckit-scaffold-spec. Not for per-spec scoping, worktree preparation, or general SDD coaching.4license: MIT5---67# SpecKit PRD89Create or update three consistent Markdown artifacts: a lean PRD for WHAT and10WHY, a technical roadmap whose SPEC catalog maps 1:1 to PRD Features, and a11roadmap-MOC that makes the spec tree navigable.1213## Ground recommendations1415Inspect the tools and skills actually available. Follow the shared16[capability-discovery](${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/capability-discovery.md)17and [grounding](${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/grounding.md) contracts. Read18applicable project instructions, `.specify/memory/constitution.md`, prior19roadmaps and decisions, and targeted code. Disclose uncertainty; do not guess.2021## Codex Skill-Selection Guard2223If Codex loaded this Claude variant, stop and follow24[`../../codex-skills/speckit-prd/SKILL.md`](../../codex-skills/speckit-prd/SKILL.md)25as the active skill. The payload builder removes this guard from Claude installs.2627## Claude interaction adapter2829In an active user chat, call `AskUserQuestion` for one question at a time. Each30call offers 2-3 mutually exclusive choices: put the grounded recommendation31first, suffix its label `(Recommended)`, and state each tradeoff briefly. Wait32for the reply before the next question.3334If no live user can answer because the skill was invoked in a background,35automation, CI, or subagent context, do not fabricate intent. A caller that36explicitly requested a draft may receive only a best-effort PRD from supplied37material, with every unvalidated decision in Open Questions and a clear38"interactive pass required" status. Do not claim the PRD is roadmap-ready and39do not create or update its roadmap or roadmap-MOC.4041## Workflow4243Read and follow the [shared PRD authoring protocol](references/prd-authoring-protocol.md)44before authoring. Determine whether the user is creating from an idea or updating45an existing PRD; before overwriting, confirm the exact output path and preserve46stable feature and SPEC identifiers for unchanged work. Use the shared47[PRD template](../speckit-coach/templates/prd-template.md),48[technical-roadmap template](../speckit-coach/templates/technical-roadmap-template.md),49[slicing heuristics](../speckit-coach/references/slicing-heuristics.md), and, for50a new roadmap, [roadmap-MOC template](../speckit-coach/templates/roadmap-moc-template.md).51If `docs/ai/specs/ubiquitous-language.md` exists, read it first and use its52terms verbatim in the PRD. Apply the protocol's interview, update,53slicing/estimation, MOC, index, and verification rules. Report created or updated paths and recommend54`/speckit-pro:speckit-scaffold-spec <SPEC-ID>` for the first ready entry.5556## Output contract5758- `docs/prd-<slug>.md`: lean PRD with Problem, Goals, Non-goals, Features and59 acceptance criteria, Migration or sequence when applicable, Module and60 Interface Deltas (required; "No module or interface changes." is an explicit61 valid entry), Constraints, Open Questions, and the 1:1 SPEC Catalog Crosswalk.62- `docs/ai/specs/<slug>-technical-roadmap.md`: ordered SPEC catalog with Source63 PRD, scope, dependencies, status, reviewability budget, module and interface64 deltas, key surfaces, and a reciprocal roadmap-MOC link.65- `docs/ai/specs/<slug>-roadmap-MOC.md`: curated epics plus the generator-owned66 `GENERATED:INDEX` zone and a relative `up:` link to the roadmap.6768This skill does not scope an existing roadmap entry (`/speckit-pro:grill-me`),69prepare a worktree or workflow (`/speckit-pro:speckit-scaffold-spec`), or teach70SDD methodology (`/speckit-pro:speckit-coach`). If the PRD already exists and71the user wants only a new roadmap, hand off to the Coach roadmap workflow.
racecraft-lab