Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文档". Combines PRD methodology with planning-with-files to avoid context switching.

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. 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 Step 1: Initialize Create the four files with templates: {scope} prd task plan.md {scope} prd notes.md {scope} prd.md {scope} tech.md Step 2: Gather Requirements Ask clarifying questions and save responses to {scope} prd notes.md : Core Questions to Ask 1. Problem : What problem are we solving? 2. Users : Who will use this? 3. Success : How do we know it's successful? 4. Constraints : Any technical/time/budget constraints? Save each answer to {scope} prd notes.md under appropriate section. Always update {scope} prd task plan.md after gathering info: Step 2.5: Context Aware Edge Case Analysis Before asking users about edge cases, scan the codebase first to infer existing patterns. This reduces redundant questions and ensures consistency with the project. Detailed reference : See references/edge case analysis.md for full scanning commands and output formats. Quick Process 1. Scan codebase for existing patterns (delete strategy, error handling, empty states, pagination) 2. Identify requirement type (CRUD, State Workflow, Async, Data Display, Form, File) 3. Generate smart assumptions patterns found in code don't need user confirmation 4. Ask only when needed no precedent, multiple patterns, or business decision required When to Ask Users Condition Action Pattern exists in codebase Auto apply, no question needed No precedent found Ask user with options Multiple conflicting patterns Ask user to choose Business rule required Ask user Output to Notes File Update {scope} prd notes.md with: Update task plan: Step 3: Research & Analysis Research best practices and save to {scope} prd notes.md : Save findings to {scope} prd notes.md → Research Findings section. Step 4: Design Solution Propose architecture with trade offs, save to {scope} prd notes.md : Step 5: Write PRD Read {scope} prd notes.md and synthesize into polished PRD: Step 6: Write Technical Design Step 7: Validate & Finalize Review with user: 1. Present PRD summary 2. Ask for feedback 3. Incorporate changes 4. Mark Phase 7 complete Important Rules Rule Bad Good Use Files Keep in memory Save to {scope} prd notes.md Update Plan Move on without update Update task plan.md with checkbox Read Before Decide Decide from memory Read notes first Separate Docs Mix PRD + Tech PRD for "what", Tech for "how" Include Options Jump to solution Document 2 3 options with pros/cons Phase Transitions Update {scope} prd task plan.md after each phase with checkbox ✓ and timestamp. Completing a PRD Mark all phases complete, set status to "✅ COMPLETE", log final deliverables. File Cleanup (Optional) After PRD is complete: Keep {scope} prd notes.md for reference (shows decision process) Archive {scope} prd task plan.md or delete Final outputs are {scope} prd.md and {scope} tech.md Quick Start Template Why This Works Problem Solution Context switching All thinking in files, read anytime Lost requirements Saved to {scope} prd notes.md immediately Inconsistent PRDs Same process, same structure "Left brain vs right brain" One coherent workflow Re explaining context Files contain full context Mixed concerns PRD (product) separate from Tech (implementation) Hidden decisions Architecture options A/B/C documented References [planning with files](../planning with files/) File based planning methodology [architecting solutions](../architecting solutions/) Non PRD solution and architecture design Edge case scanning: references/edge case analysis.md Auto Trigger (Follow up Metadata) When this skill completes, record or run supported follow ups: 1. self improving agent (background) Propose reusable patterns 2. session logger (auto) Save session context when supported

prd-planner