PRD Generator

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

Workspace Mode Note

When running in workspace mode, save PRDs to .aha-loop/tasks/ instead of tasks/. The orchestrator will provide the actual paths in the prompt context.

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

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
• Research Topics: Questions to investigate before implementation (for complex stories)

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

Format:

markdown
1### US-001: [Title]
2**Description:** As a [user], I want [feature] so that [benefit].
3
4**Research Topics:** (optional, for complex stories)
5- [ ] Question about technology choice or best practice
6- [ ] Question about existing patterns in codebase
7- [ ] Question about third-party library usage
8
9**Acceptance Criteria:**
10- [ ] Specific verifiable criterion
11- [ ] Another criterion
12- [ ] Typecheck/lint passes
13- [ ] **[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.
• Research Topics help the research phase focus on the right questions. Include them when:
  • Using an unfamiliar third-party library
  • Multiple implementation approaches exist
  • Performance or scalability concerns
  • Complex integration with existing systems

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)

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**Description:** As a developer, I need to store task priority so it persists across sessions.
18
19**Research Topics:**
20- [ ] Best practices for database enum fields in this stack
21- [ ] Migration rollback strategies for schema changes
22
23**Acceptance Criteria:**
24- [ ] Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
25- [ ] Generate and run migration successfully
26- [ ] Typecheck passes
27
28### US-002: Display priority indicator on task cards
29**Description:** As a user, I want to see task priority at a glance so I know what needs attention first.
30
31**Research Topics:**
32- [ ] Accessible color schemes for priority indicators (WCAG compliance)
33- [ ] Existing badge/tag components in codebase to reuse
34
35**Acceptance Criteria:**
36- [ ] Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
37- [ ] Priority visible without hovering or clicking
38- [ ] Typecheck passes
39- [ ] Verify in browser using dev-browser skill
40
41### US-003: Add priority selector to task edit
42**Description:** As a user, I want to change a task's priority when editing it.
43
44**Acceptance Criteria:**
45- [ ] Priority dropdown in task edit modal
46- [ ] Shows current priority as selected
47- [ ] Saves immediately on selection change
48- [ ] Typecheck passes
49- [ ] Verify in browser using dev-browser skill
50
51### US-004: Filter tasks by priority
52**Description:** As a user, I want to filter the task list to see only high-priority items when I'm focused.
53
54**Research Topics:**
55- [ ] URL state management patterns in this codebase
56- [ ] Existing filter implementations to follow as pattern
57
58**Acceptance Criteria:**
59- [ ] Filter dropdown with options: All | High | Medium | Low
60- [ ] Filter persists in URL params
61- [ ] Empty state message when no tasks match filter
62- [ ] Typecheck passes
63- [ ] Verify in browser using dev-browser skill
64
65## Functional Requirements
66
67- FR-1: Add `priority` field to tasks table ('high' | 'medium' | 'low', default 'medium')
68- FR-2: Display colored priority badge on each task card
69- FR-3: Include priority selector in task edit modal
70- FR-4: Add priority filter dropdown to task list header
71- FR-5: Sort by priority within each status column (high to medium to low)
72
73## Non-Goals
74
75- No priority-based notifications or reminders
76- No automatic priority assignment based on due date
77- No priority inheritance for subtasks
78
79## Technical Considerations
80
81- Reuse existing badge component with color variants
82- Filter state managed via URL search params
83- Priority stored in database, not computed
84
85## Success Metrics
86
87- Users can change priority in under 2 clicks
88- High-priority tasks immediately visible at top of lists
89- No regression in task list performance
90
91## Open Questions
92
93- Should priority affect task ordering within a column?
94- Should we add keyboard shortcuts for priority changes?

Checklist

Before saving the PRD:

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

Research Topics Guidelines

When adding research topics, consider:

Good research topics:

• "How does library X handle Y?" (specific, answerable)
• "What existing patterns does this codebase use for Z?"
• "Performance implications of approach A vs B"
• "Best practices for implementing feature X"

Bad research topics:

• "How to code this" (too vague)
• "Make it work" (not a question)
• "Everything about library X" (too broad)

When to include research topics:

• First time using a library in this project
• Multiple valid approaches exist
• Performance-sensitive implementation
• Security-sensitive implementation
• Complex integration with external systems