Generate a stakeholder-facing PRD from a design doc. Use when you have a finalized design doc and need a non-technical product requirements document for archival or sharing. Triggers on /prd, 'generate PRD', 'write a PRD', 'product requirements'.
All subagent dispatches use disk-mediated dispatch. See shared/dispatch-convention.md for the full protocol.
Generates a Product Requirements Document (PRD) from a finalized design doc. The PRD reformats technical design decisions into stakeholder-friendly language — problem statement, user stories, requirements, scope, success metrics.
Announce at start: "I'm using the PRD skill to generate a product requirements document."
Core principle: The PRD derives everything from the design doc. It does not introduce new decisions or requirements — it translates existing technical decisions for a non-technical audience.
/design or /build Phase 1 completes — you have a finalized design docThe skill needs a design doc path. If not provided, it searches:
/prd docs/plans/2026-03-23-my-feature-design.mddocs/plans/ for the most recently modified *-design.md fileskills/build/prd-writer-prompt.md
docs/prds/YYYY-MM-DD-<topic>-prd.mddocs: add PRD for [feature]The generated PRD follows a fixed structure:
Called by:
Standalone usage:
/prd <design-doc-path> — generate PRD from any design doc/prd (no args) — auto-detect most recent design docPrompt template: skills/build/prd-writer-prompt.md (shared with build pipeline)