create-prd

name	create-prd
description	Create Product Requirements Documents (PRDs) from feature requests using a required clarify-plan-draft-save workflow. Use when Codex is asked to write, generate, create, draft, or update a PRD, product requirements document, product spec, feature requirements document, or requirements artifact that should be saved as tasks/prd-[feature-name]/prd.md.

Create PRD

Use this skill to produce clear, actionable PRDs for development and product teams.

Required Workflow

1. Clarify before drafting.

   • Ask clarifying questions before generating the PRD.
   • Cover the problem, goals, users, main functionality, constraints, dependencies, and what is not in scope.
   • Use the user-question tool when available; otherwise ask concise questions directly.

2. Plan before drafting.

   • Create a brief section-by-section PRD development plan after the user answers.
   • Identify assumptions, dependencies, and open risks.
   • Use web search for current business rules, regulations, third-party policy constraints, or other facts that may have changed.

3. Draft the PRD.

   • Read references/prd-template.md and follow it exactly.
   • Focus on the WHAT and WHY, not implementation details.
   • Include numbered functional requirements in the Main Features section.
   • Keep the main PRD to 2,000 words or fewer.
   • Include usability and accessibility requirements.

4. Save the PRD.

   • Create ./tasks/prd-[feature-name]/, where [feature-name] is a kebab-case name derived from the feature.
   • Save the final document as ./tasks/prd-[feature-name]/prd.md.

5. Report results.

   • Provide the final file path.
   • Give a very brief summary of the PRD outcome.

Hard Rules

• Do not generate the PRD before asking clarifying questions.
• Do not deviate from the template in references/prd-template.md.
• Do not include implementation details, technical design, code, task breakdowns, or low-level architecture in the PRD.
• Do not skip saving the file unless the user explicitly asks for draft text only.

Quality Checklist

• Clarifying questions were asked and answered.
• A PRD development plan was created before drafting.
• The PRD follows references/prd-template.md.
• Functional requirements are numbered.
• The file is saved at ./tasks/prd-[feature-name]/prd.md.
• The final response includes the saved path and a very brief summary.