Generate Product Requirements Documents (PRDs) in Markdown format. Use when users want to create a PRD, spec out a feature, document requirements, or plan new functionality. Triggers on requests like "create a PRD", "write requirements for", "spec out this feature", or "document this feature idea".
Create clear, actionable Product Requirements Documents suitable for junior developers to understand and implement.
/tasks/prd-[feature-name].mdImportant: Do NOT implement the feature. Only create the PRD document.
Ask only critical questions where the initial prompt is ambiguous. Skip questions when answers are reasonably inferable.
Question areas:
Format requirements:
Example:
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Generate additional revenue
2. Who is the target user?
A. New users only
B. Existing users only
C. All users
D. Admin users only
3. What is the expected scope?
A. MVP - minimal viable implementation
B. Full feature - complete functionality
C. Iteration - enhance existing feature
After receiving answers, generate the PRD using the structure in references/prd-template.md.
Writing guidelines:
Save to /tasks/prd-[feature-name].md
Use kebab-case for feature name (e.g., prd-user-authentication.md, prd-export-dashboard.md).
Create the /tasks/ directory if it doesn't exist.