PRD Generator

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

The Job

1. Receive a feature description from the user
2. Ask 3-5 essential clarifying questions (with lettered options)
3. Generate a structured PRD based on answers
4. Save to docs/prd.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:

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
1### US-001: [Title]
2
3**Description:** As a [user], I want [feature] so that [benefit].
4
5**Acceptance Criteria:**
6
7- [ ] Specific verifiable criterion
8- [ ] Another criterion
9- [ ] Typecheck/lint passes
10- [ ] **[UI stories only]** Verify in browser using dev-browser skill

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 using dev-browser skill" as acceptance criteria. This ensures visual verification of frontend work.

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

Archiving Previous PRDs

Before writing a new docs/prd.md, check if there is an existing one from a different feature:

1. Read the current docs/prd.md if it exists
2. Check if it's for a different feature than what you're about to create
3. If different:
   • Extract feature name from PRD title/intro
   • Check if archive folder already exists: look for archive/*-feature-name/
   • If found, use existing folder; if not, create archive/YYYY-MM-DD-feature-name/
   • Copy current docs/prd.md to archive folder
   • Write the new PRD to docs/prd.md

Shared archive folders: Multiple runs of same feature (across dates) share one archive folder. Prevents duplicate archives when PRD skill and task skill run on different days.

Output

• Format: Markdown (.md)
• Location: docs/
• Filename: docs/prd.md

Example PRD

markdown
1# PRD: Task Priority System
2
3## Introduction
4
5Add priority levels to tasks so users can focus on what matters most. Tasks can be marked as high, medium, or low priority, with visual indicators and filtering to help users manage their workload effectively.
6
7## Goals
8
9- Allow assigning priority (high/medium/low) to any task
10- Provide clear visual differentiation between priority levels
11- Enable filtering and sorting by priority
12- Default new tasks to medium priority
13
14## User Stories
15
16### US-001: Add priority field to database
17
18**Description:** As a developer, I need to store task priority so it persists across sessions.
19
20**Acceptance Criteria:**
21
22- [ ] Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
23- [ ] Generate and run migration successfully
24- [ ] Typecheck passes
25
26### US-002: Display priority indicator on task cards
27
28**Description:** As a user, I want to see task priority at a glance so I know what needs attention first.
29
30**Acceptance Criteria:**
31
32- [ ] Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
33- [ ] Priority visible without hovering or clicking
34- [ ] Typecheck passes
35- [ ] Verify in browser using dev-browser skill
36
37### US-003: Add priority selector to task edit
38
39**Description:** As a user, I want to change a task's priority when editing it.
40
41**Acceptance Criteria:**
42
43- [ ] Priority dropdown in task edit modal
44- [ ] Shows current priority as selected
45- [ ] Saves immediately on selection change
46- [ ] Typecheck passes
47- [ ] Verify in browser using dev-browser skill
48
49### US-004: Filter tasks by priority
50
51**Description:** As a user, I want to filter the task list to see only high-priority items when I'm focused.
52
53**Acceptance Criteria:**
54
55- [ ] Filter dropdown with options: All | High | Medium | Low
56- [ ] Filter persists in URL params
57- [ ] Empty state message when no tasks match filter
58- [ ] Typecheck passes
59- [ ] Verify in browser using dev-browser skill
60
61## Functional Requirements
62
63- FR-1: Add `priority` field to tasks table ('high' | 'medium' | 'low', default 'medium')
64- FR-2: Display colored priority badge on each task card
65- FR-3: Include priority selector in task edit modal
66- FR-4: Add priority filter dropdown to task list header
67- FR-5: Sort by priority within each status column (high to medium to low)
68
69## Non-Goals
70
71- No priority-based notifications or reminders
72- No automatic priority assignment based on due date
73- No priority inheritance for subtasks
74
75## Technical Considerations
76
77- Reuse existing badge component with color variants
78- Filter state managed via URL search params
79- Priority stored in database, not computed
80
81## Success Metrics
82
83- Users can change priority in under 2 clicks
84- High-priority tasks immediately visible at top of lists
85- No regression in task list performance
86
87## Open Questions
88
89- Should priority affect task ordering within a column?
90- Should we add keyboard shortcuts for priority changes?

Checklist

Before saving the PRD:

• Archived previous PRD (if docs/prd.md exists for a different feature, archive it first)
• 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 docs/prd.md