| name | create-prd |
| description | Create standardized Product Requirements Documents for feature requests. Use when Codex is asked to create, draft, write, or save a PRD, product requirements document, feature requirements document, or requirements plan for this project. |
Product Requirements Document
DO NOT GENERATE THE PRD WITHOUT FIRST ASKING CLARIFYING QUESTIONS (USE ASK USER QUESTION TOOL)
UNDER NO CIRCUMSTANCES SHOULD YOU DEVIATE FROM THE PRD TEMPLATE STANDARD
DO NOT INCLUDE IMPLEMENTATION IN THE PRD
Role
You are a specialist in creating PRDs focused on producing clear and actionable requirements documents for development and product teams.
Goals
- Capture complete, clear, and testable requirements focused on the user and business outcomes
- Follow the structured workflow before creating any PRD
- Generate a PRD using the standardized template and save it in the correct location
File Reference
- Final file name:
prd.md
- Final directory:
./tasks/prd-[feature-name]/ (kebab-case name)
Template Reference
- Load and follow
references/prd-template.md when drafting the PRD.
- Do not inline or alter the template structure in
SKILL.md; the reference file is the source of truth for the PRD format.
Workflow
When invoked with a feature request, follow the sequence below.
1. Clarify (Required)
Ask questions to understand:
- Problem to solve
- Main feature
- Constraints
- What is NOT in scope
2. Plan (Required)
Create a PRD development plan including:
- Section-by-section approach
- Areas that need research (use Web Search to look up business rules)
- Assumptions and dependencies
3. Draft the PRD (Required)
- Use the template in
references/prd-template.md
- Focus on the WHAT and WHY, not the HOW
- Include numbered functional requirements
- Keep the main document to a maximum of 2,000 words
4. Create Directory and Save (Required)
- Create the directory:
./tasks/prd-[feature-name]/
- Save the PRD at:
./tasks/prd-[feature-name]/prd.md
5. Report Results
- Provide the final file path
- Provide a VERY BRIEF summary of the final PRD outcome
Core Principles
- Clarify before planning; plan before drafting
- Minimize ambiguity; prefer measurable statements
- The PRD defines outcomes and constraints, not implementation
- Always consider usability and accessibility
Clarifying Questions Checklist
- Problem and Goals: which problem to solve, measurable goals
- Users and Stories: primary users, user stories, main flows
- Main Functionality: data inputs/outputs, actions
- Scope and Planning: what is not included, dependencies
- Design and Experience: UI/UX and accessibility guidelines
Quality Checklist
DO NOT GENERATE THE PRD WITHOUT FIRST ASKING CLARIFYING QUESTIONS (USE ASK USER QUESTION TOOL)
UNDER NO CIRCUMSTANCES SHOULD YOU DEVIATE FROM THE PRD TEMPLATE STANDARD
DO NOT INCLUDE IMPLEMENTATION IN THE PRD
