Generate PRD

Turn either a finalized discussion or a user brief into a PRD. Prefer a finalized FINAL.md (at .plans/discussion/<topic>/FINAL.md) when available — the discussion already resolved the design tree, so the PRD is mostly a translation step rather than a fresh interview.

Inputs and outputs

One PRD comes from exactly one FINAL.md. This skill never aggregates multiple discussions into a single PRD — each invocation processes one discussion topic. If the user wants a PRD that spans multiple discussions, they should first merge them into a single discussion topic and finalize that one FINAL.md.

• Input (preferred): <cwd>/.plans/discussion/<topic>/FINAL.md — a finalized design-discussion summary, identified by _Status: finalized_ in the topic's STATE.md. Exactly one topic per PRD.
• Input (fallback): user brief + inline interview (when no FINAL.md exists).
• Output: <cwd>/.plans/<feature>/prd.md. The <feature> slug must equal the source <topic> slug when sourcing from FINAL.md, so the discussion and PRD stay linked 1:1.
• Draft checkpoint: <cwd>/.plans/<feature>/prd-draft.md — incrementally rewritten after each major step so a mid-skill interruption is recoverable.

No GitHub issue is created. The user can post manually if they choose.

See MAPPING.md for the FINAL.md → PRD section-by-section mapping rules.

Workflow