Create PRD
Create a detailed Product Requirements Document (PRD) in Markdown format.
When to use
- •When starting a new feature or initiative
- •When you need to document requirements for development
- •Before task generation
Process
- •Receive initial prompt: Brief description of the feature
- •Ask clarifying questions: 3-5 essential questions with lettered options (A, B, C, D)
- •Generate PRD: Based on prompt and answers
- •Save PRD: As
prd-[feature-name].mdin the/prd/directory
PRD sections
- •Introduction/Overview
- •Goals
- •User Stories
- •Functional Requirements (numbered)
- •Non-Goals (Out of Scope)
- •Design Considerations (optional)
- •Technical Considerations (optional)
- •Success Metrics
- •Open Questions
Rules
- •Do NOT start implementing the PRD
- •Always ask clarifying questions first
- •Take the user's answers and improve the PRD
- •Target audience: junior developer (explicit, unambiguous requirements)
For the full process, question guidelines, and structure details, see references/create-prd.md.
Follow the writing standards in _shared/writing-standards.md for all outputs.