| name | prd-writer |
| description | Create a clear, actionable PRD with clarifying questions and a junior-friendly structure. |
PRD Writer
Goal
Create a detailed Product Requirements Document (PRD) in Markdown from an initial feature prompt, suitable for a junior developer.
Process
- Receive initial prompt from user.
- Ask clarifying questions before writing. Provide options in letter/number lists for easy replies.
- Generate the PRD using the structure below.
- Save as
[n]-prd-[feature-name].md under /tasks/ where n is zero‑padded (e.g., 0001-prd-user-authentication.md).
Clarifying questions (guide)
- Problem/Goal: What problem does this solve? What is the main goal?
- Target User: Who is the primary user?
- Core Functionality: Key actions the user must perform?
- User Stories: Provide a few stories (As a…, I want…, so that…)
- Acceptance Criteria: How do we know it’s done/successful?
- Scope/Boundaries: Any explicit non-goals?
- Data Requirements: What data to display/manipulate?
- Design/UI: Any mockups/guidelines? Desired look/feel?
- Edge Cases: Potential edge cases and error conditions?
PRD Structure
- Introduction/Overview
- Goals
- User Stories
- Functional Requirements (numbered)
- Non-Goals (Out of Scope)
- Design Considerations (Optional)
- Technical Considerations (Optional)
- Success Metrics
- Open Questions
Output
- Format: Markdown (.md)
- Location:
/tasks/
- Filename pattern:
[n]-prd-[feature-name].md
Interaction
- Always ask clarifying questions before writing.
- Incorporate the answers and refine the PRD accordingly.
References
