Plan PRD

Create a comprehensive Product Requirements Document.

When to Use

• Large features or epics
• New user-facing functionality
• Features requiring UX exploration

Artifacts

• PRD-[EPIC-NAME].md in docs/working/
• task.md updated via task_boundary

Approach

Phase 1: Discovery & Scope

1. Proof of Understanding: Summarize core user problem in one sentence.
2. User Stories: "As a [user], I want [action], so that [benefit]"
3. Non-Goals: Explicitly state out-of-scope items.