prd-planner

PRD Planner

A PRD creation skill that uses persistent file-based planning to maintain coherent thinking and avoid "left-brain vs right-brain" context switching issues.

When This Skill Activates

This skill activates when you:

• Explicitly say "PRD", "prd", "create a PRD", or "产品需求文档"
• Say "product requirements document" or "产品需求"
• Mention "write a PRD for..."
• Say "PRD planning" or "PRD 设计"

If user says "design solution" or "architecture design" without mentioning PRD, use architecting-solutions instead.

The Core Philosophy

"PRD creation should be traceable, coherent, and persistent - not scattered across context switches."

This skill combines:

• PRD methodology (from architecting-solutions)
• File-based persistence (from planning-with-files)

To create a single, coherent PRD creation workflow that doesn't lose context.

4-File Pattern for PRD Creation

For every PRD project, create FOUR files:

Pick a SCOPE (short, unique, kebab-case slug) and use it as a prefix for all files.

docs/{scope}-prd-notes.md     → Store research, requirements, findings, options
docs/{scope}-prd-task-plan.md → Track PRD creation phases and progress
docs/{scope}-prd.md           → Product requirements (what & why)
docs/{scope}-tech.md          → Technical design (how)

File Purposes

File	Purpose	Audience	Updated When
{scope}-prd-notes.md	Raw research, requirements, architecture options (A/B/C)	Self + reviewers	New information gathered
{scope}-prd-task-plan.md	Track progress, phases, checkboxes, timestamps	PM + dev lead	Each phase completion
{scope}-prd.md	Product requirements (what & why), user flows	PM + stakeholders + devs	After requirements are clear
{scope}-tech.md	Technical design (API, data flow, implementation)	Developers + architects	After architecture is decided

Workflow

┌─────────────────────────────────────────────────────────────────┐
│                     PRD Creation Workflow                       │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  1. Initialize → Create 4 files with template                   │
│  2. Requirements → Gather to {scope}-prd-notes.md               │
│  2.5 Edge Cases → Scan codebase, infer patterns, ask smartly    │
│  3. Analysis → Research best practices, save to notes           │
│  4. Design → Propose architecture options (A/B/C), save to notes │
│  5. PRD → Write product requirements to {scope}-prd.md          │
│  6. Tech → Write technical design to {scope}-tech.md            │
│  7. Validate → Review with user, finalize                       │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘
                    ↓
           All thinking persisted to files
                    ↓
              No context switching