| name | to-prd |
| description | Documentation phase. Synthesizes the current conversation into a formal Product Requirements Document (PRD). Trigger: "/to-prd", "create PRD", "write a PRD for this".
|
To PRD Skill
Convert the current context and agreed-upon decisions into a structured PRD.
PRD Structure
- Summary: One-paragraph overview of the goal.
- Problem Statement: Why are we doing this?
- Goals: What does success look like?
- Out of Scope: What are we NOT doing?
- Technical Design: High-level architectural decisions.
- User Stories / Requirements: Concrete functional requirements.
Rules
- Use the exact terminology agreed upon during the "Grill" phase.
- File the PRD in the
docs/ folder or as a GitHub issue.
- Keep it technical and concise.