Generate a PRD (Product Requirements Document) for a new project. Exclude all visual/UI content and focus on core goals and requirements.

The PRD serves as the reference point for all subsequent documents (SPEC, FEATURE_LIST, FEATURE_PLAN). An unclear PRD causes confusion at every downstream stage, so clarity here is critical.

When to Apply

Starting a new project
Existing project has no PRD
User invokes /init

Process

Step 1: Gather Requirements

If the description is unclear, ask up to 3 targeted questions:

What is the core problem this project solves?
Who is the target user?
Any key constraints (tech, timeline, team)?

Wait for user response before proceeding.

Step 2: Scan Project Root

Check existing state:

Generate a PRD (Product Requirements Document) for a new project. Exclude all visual/UI content and focus on core goals and requirements.

The PRD serves as the reference point for all subsequent documents (SPEC, FEATURE_LIST, FEATURE_PLAN). An unclear PRD causes confusion at every downstream stage, so clarity here is critical.

When to Apply

Starting a new project
Existing project has no PRD
User invokes /init

Process

Step 1: Gather Requirements

If the description is unclear, ask up to 3 targeted questions:

What is the core problem this project solves?
Who is the target user?
Any key constraints (tech, timeline, team)?

Wait for user response before proceeding.

Step 2: Scan Project Root

Check existing state:

Init — PRD Creation

When to Apply

Process

Step 1: Gather Requirements

Step 2: Scan Project Root

Init — PRD Creation

When to Apply

Process

Step 1: Gather Requirements

Step 2: Scan Project Root

Step 3: Generate docs/PRD.md

Step 4: Request Review

Quality Rules

My Workflow

Create Instructions

Init

Everything Claude Code Conventions

Codebase Onboarding

Ui Demo