Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Create detailed PRDs that are clear, actionable, and suitable for autonomous implementation by Ralph.
tasks/prd-[feature-name].mdDo NOT start implementing. Just create the PRD.
Ask only critical questions. Format with lettered options so users can respond with "1A, 2C, 3B":
1. What is the primary goal?
A. Option one
B. Option two
C. Other: [please specify]
Focus on: Problem/Goal, Core Functionality, Scope/Boundaries, Success Criteria.
Brief description of the feature and the problem it solves.
Specific, measurable objectives (bullet list).
Each story must be small enough to complete in one Codex context window.
Format:
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific verifiable criterion
- [ ] Another criterion
- [ ] Typecheck/lint passes
- [ ] **[UI stories only]** Verify in browser
Acceptance criteria must be verifiable, not vague. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good.
Numbered list: "FR-1: The system must..."
What this feature will NOT include.
Known constraints, dependencies, performance requirements.
How success is measured.
Remaining questions or areas needing clarification.
The PRD reader is an AI agent (Codex) with fresh context each iteration:
tasks/prd-[feature-name].md (kebab-case)tasks/prd-[feature-name].md