Goal: Draft a PRD focusing on what and why, not how. No code.
HARD-GATE
- No code, pseudo-code, SQL, class names, or method signatures.
- Resolve newly introduced product scope before implementation. Existing approval or a concrete user-authorized brief remains valid; this skill produces a PRD, not implementation code.
Core Process
- Receive feature description.
- Clarify only if ambiguous — use up to 5 questions from assets/prd_questions.md.
- Draft using PRD_TEMPLATE.md section by section.
- Validate — present the PRD; request a decision on unresolved product scope before implementation.
Output
- Save to
/tasks/prd-<slug>.md(kebab-case). - Write requirements in natural language — no code.
- Reuse prior approval when scope is unchanged; otherwise request the specific scope decision. After approval, use
plan-ticketsto draft tracker-ready work items.
Integration
| Skill | When |
|---|---|
plan-tickets |
Draft tracker-ready work items after PRD approval |