PRD Generator

Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.

The Job

•Receive a feature description from the user
•Ask 3-5 essential clarifying questions (with lettered options)
•Generate a structured PRD based on answers
•Save to tasks/prd-[feature-name].md

Important: Do NOT start implementing. Just create the PRD.

Step 1: Clarifying Questions

Ask only critical questions where the initial prompt is ambiguous. Focus on:

•Problem/Goal: What problem does this solve?
•Core Functionality: What are the key actions?
•Scope/Boundaries: What should it NOT do?
•Success Criteria: How do we know it's done?

Format Questions Like This:

code

1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Other: [please specify]

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 scope?
   A. Minimal viable version
   B. Full-featured implementation
   C. Just the backend/API
   D. Just the UI

This lets users respond with "1A, 2C, 3B" for quick iteration.

Step 2: PRD Structure

Generate the PRD with these sections:

1. Introduction/Overview

Brief description of the feature and the problem it solves.

2. Goals

Specific, measurable objectives (bullet list).

3. User Stories

Each story needs:

•Title: Short descriptive name
•Description: "As a [user], I want [feature] so that [benefit]"
•Acceptance Criteria: Verifiable checklist of what "done" means

Each story should be small enough to implement in one focused session.

Format:

markdown

### 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

Important:

•Acceptance criteria must be verifiable, not vague. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good.
•For any story with UI changes: Always include "Verify in browser" as acceptance criteria.

4. Functional Requirements

Numbered list of specific functionalities:

•"FR-1: The system must allow users to..."
•"FR-2: When a user clicks X, the system must..."

Be explicit and unambiguous.

5. Non-Goals (Out of Scope)

What this feature will NOT include. Critical for managing scope.

6. Design Considerations (Optional)

•UI/UX requirements
•Link to mockups if available
•Relevant existing components to reuse

7. Technical Considerations (Optional)

•Known constraints or dependencies
•Integration points with existing systems
•Performance requirements

8. Success Metrics

How will success be measured?

•"Reduce time to complete X by 50%"
•"Increase conversion rate by 10%"

9. Open Questions

Remaining questions or areas needing clarification.

Writing for Junior Developers

The PRD reader may be a junior developer or AI agent. Therefore:

•Be explicit and unambiguous
•Avoid jargon or explain it
•Provide enough detail to understand purpose and core logic
•Number requirements for easy reference
•Use concrete examples where helpful

Output

•Format: Markdown (.md)
•Location: tasks/
•Filename: prd-[feature-name].md (kebab-case)

Checklist

Before saving the PRD:

• Asked clarifying questions with lettered options
• Incorporated user's answers
• User stories are small and specific
• Functional requirements are numbered and unambiguous
• Non-goals section defines clear boundaries
• Saved to tasks/prd-[feature-name].md