PRD Generator

Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation with the Ralph autonomous agent system.

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:

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.

This is CRITICAL for Ralph to work properly. If stories are too big, the AI will run out of context before finishing.

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 using dev-browser skill

Right-sized stories:

• Add a database column and migration

• Add a UI component to an existing page

• Update a server action with new logic

• Add a filter dropdown to a list

API 包粒度原则（API-First）：后端功能拆分时，每个独立业务功能应作为一个 API 包来设计。一个 User Story 可以是"开发某 API 包 + 生成其 API 文档"，后续前端 Story 只需"依据 API 文档实现页面调用"。Story 应标注所属层级（[后端] /[前端] /[中间层] /[文档] /[集成] ），确保跨层任务的解耦和按序执行。

Too big (split these):

• "Build the entire dashboard"

• "Add authentication"

• "Refactor the API"

• "Add SSE streaming" → 应拆为: [后端] SSE端点API包, [文档] SSE接口文档, [前端] EventSource消费+渲染, [集成] 端到端验证

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 AI Agents

The PRD will be read by Claude Code (Ralph). 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

Story Ordering: Dependencies First

Stories execute in priority order. Earlier stories must NOT depend on later ones.

Correct order (API-First 原则):

• Schema/database changes (migrations)

• Server actions / backend logic → 封装为独立 API 包

• API 文档生成（端点、参数、响应、错误码、示例）

• UI components that consume the API (依据 API 文档开发)

• Integration layer / BFF (多 API 编排，如需要)

• Dashboard/summary views that aggregate data

Wrong order:

• UI component (depends on schema that does not exist yet)

• Schema change

• Frontend calling API that has no documentation yet

Output

• Format: Markdown (.md )

• Location: tasks/

• Filename: prd-[feature-name].md (kebab-case)

Ensure the tasks/ directory exists before saving.

Example PRD

PRD: Task Priority System

Introduction

Add 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.

Goals

• Allow assigning priority (high/medium/low) to any task
• Provide clear visual differentiation between priority levels
• Enable filtering and sorting by priority
• Default new tasks to medium priority

User Stories

US-001: Add priority field to database

Description: As a developer, I need to store task priority so it persists across sessions.

Acceptance Criteria:

• Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
• Generate and run migration successfully
• Typecheck passes

US-002: Display priority indicator on task cards

Description: As a user, I want to see task priority at a glance so I know what needs attention first.

Acceptance Criteria:

• Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
• Priority visible without hovering or clicking
• Typecheck passes
• Verify in browser using dev-browser skill

US-003: Add priority selector to task edit

Description: As a user, I want to change a task's priority when editing it.

Acceptance Criteria:

• Priority dropdown in task edit modal
• Shows current priority as selected
• Saves immediately on selection change
• Typecheck passes
• Verify in browser using dev-browser skill

US-004: Filter tasks by priority

Description: As a user, I want to filter the task list to see only high-priority items when I'm focused.

Acceptance Criteria:

• Filter dropdown with options: All | High | Medium | Low
• Filter persists in URL params
• Empty state message when no tasks match filter
• Typecheck passes
• Verify in browser using dev-browser skill

Functional Requirements

• FR-1: Add priority field to tasks table ('high' | 'medium' | 'low', default 'medium')
• FR-2: Display colored priority badge on each task card
• FR-3: Include priority selector in task edit modal
• FR-4: Add priority filter dropdown to task list header
• FR-5: Sort by priority within each status column (high to medium to low)

Non-Goals

• No priority-based notifications or reminders
• No automatic priority assignment based on due date
• No priority inheritance for subtasks

Technical Considerations

• Reuse existing badge component with color variants
• Filter state managed via URL search params
• Priority stored in database, not computed

Success Metrics

• Users can change priority in under 2 clicks
• High-priority tasks immediately visible at top of lists
• No regression in task list performance

Open Questions

• Should priority affect task ordering within a column?
• 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 (completable in one session)

• User stories are ordered by dependencies

• Functional requirements are numbered and unambiguous

• Non-goals section defines clear boundaries

• UI stories include "Verify in browser using dev-browser skill"

• Saved to tasks/prd-[feature-name].md