| name | create-prd |
| description | Create Product Requirements Documents from feature ideas or product requests. Use when Codex is asked to create, draft, generate, or save a PRD; turn a feature request into requirements; define goals, user stories, scope, user experience, or product constraints; or create files under tasks/prd-[feature-name]/prd.md. |
Create PRD
Core Workflow
Use this skill to turn a feature request into a clear, actionable PRD saved in the project task structure.
Read resources/create-prd.md before starting. Treat that file as the canonical workflow for this skill.
Load resources/prd-template.md only after clarification and planning, when drafting the PRD. Treat that file as the required PRD template standard.
Execution Rules
- Ask clarifying questions before drafting any PRD.
- Create a brief PRD development plan after the clarifying answers are available.
- Use web search when business rules, regulations, current market behavior, or external product constraints need verification.
- Generate the PRD from the exact template in
resources/prd-template.md.
- Focus on what and why; do not include implementation details.
- Keep functional requirements numbered.
- Save the final PRD to
tasks/prd-[feature-name]/prd.md, where [feature-name] is kebab-case.
- Report the final file path and a very brief outcome summary.
Expected Inputs
Typical input is a feature idea, product request, rough user story, or request such as:
- "Use $create-prd to create a PRD for user profile editing."
- "Draft a PRD for adding team invitations."
- "Create requirements for a checkout flow and save the PRD."
If the feature name is unclear, derive a concise kebab-case name from the request after clarification.
