AgentSkillsCN

CraftPRD

从模糊构想到结构化需求文档的PRD生命周期。适用于设计产品、撰写PRD、评审PRD、梳理PRD结构、重构PRD、验证PRD、检查一致性、核对PRD、执行各项检查、制作一页纸概要、识别“过于复杂”问题、捕捉复杂性信号、拆分PRD、整理流程发现、修复发现，或全面审视各项发现。

SKILL.md
--- frontmatter
name: CraftPRD
description: PRD lifecycle from vague idea to structured spec. USE WHEN design product OR write PRD OR review PRD OR structure PRD OR restructure PRD OR validate PRD OR check consistency OR verify PRD OR run checks OR one-pager OR "too complex" OR complexity signals OR split PRD OR process findings OR fix findings OR go through findings.

CraftPRD

Guides the full PRD lifecycle: from vague idea through one-pager to structured technical specification. Detects when a monolithic PRD has outgrown prose and helps split it into the right mediums (code, state machine, prose).

Core Principle

Prose for decisions and rationale. Code for contracts and consistency. State machines for transitions. Don't express technical specs in the wrong medium.

A PRD naturally grows from a one-pager into a technical spec. At some point (~500-800 lines), it starts containing TypeScript interfaces, SQL schemas, and state machine diagrams in markdown. This is the complexity threshold — the signal to restructure into proper mediums where compilers, not humans, enforce consistency.

Workflow Routing

WorkflowTriggerFile
Explore"vague idea", "new product idea", "let's think about"Workflows/Explore.md
Draft"write it up", "capture this", "one-pager"Workflows/Draft.md
Deepen"flesh out", "add detail", "iterate on PRD"Workflows/Deepen.md
Structure"structure this", "split PRD", "restructure", "too complex"Workflows/Structure.md
Validate"validate PRD", "check consistency", "verify PRD", "run checks"Workflows/Validate.md
Review"review PRD", "find issues", "consistency check"Workflows/Review.md
ProcessFindings"process findings", "fix findings", "go through findings"Workflows/ProcessFindings.md

Lifecycle Overview

code
Explore → Draft → Deepen ──→ Structure → Validate → Review → ProcessFindings
 (idea)  (1-pager) (iterate)  ⚠️ threshold (checks)  (verify)   (fix)
                      │                        │          │          │
                      └── complexity signals ───┘         │          │
                           trigger Structure              │          │
                                                  ┌──────┘──────────┘
                                                  ↓
                                           Review again (verify fixes)

Validate vs Review:

  • •Validate = deterministic checklist (fast, cheap, mechanical). Catches cross-reference errors, missing fields, broken imports.
  • •Review = expert judgment (slow, thorough, creative). Catches design flaws, trade-off concerns, missing considerations.

Structure workflow adapts to PRD size:

  • •Growing PRD (~500 lines): proactive — "split these sections now before it grows"
  • •Mature PRD (~3000 lines): retroactive — "untangle, migration plan, step-by-step restructure"

Key References

  • •UsualSuspects — Areas to analyze when destructuring a PRD (domain model, state machine, API contract, framework decisions)
  • •ComplexitySignals — How to detect when a PRD needs restructuring
  • •MediumGuide — What belongs in code vs prose vs state machine vs config

Examples

Example 1: Start from scratch

code
User: "I have an idea for a review pipeline tool"
→ Invokes Explore workflow
→ Structured discussion, captures decisions
→ Output: discussion notes file

Example 2: Write up an idea

code
User: "Let's write up that review pipeline idea as a one-pager"
→ Invokes Draft workflow
→ Creates one-pager PRD from discussion notes
→ Output: one-pager PRD file

Example 3: PRD getting complex

code
User: "This PRD has grown to 2000 lines and I keep finding inconsistencies"
→ Invokes Structure workflow
→ Analyzes PRD for complexity signals
→ Walks through "usual suspects" area by area
→ Produces migration plan
→ Executes restructuring step by step

Example 4: Review structured spec

code
User: "Review this PRD for inconsistencies"
→ Invokes Review workflow
→ Cross-checks types, state machine, API contract
→ Reports findings by severity

Example 5: Validate structured spec

code
User: "Validate this PRD" (after Structure)
→ Invokes Validate workflow
→ Discovers code files, classifies patterns
→ Launches 3 parallel checker agents (cross-ref, completeness, types)
→ Reports pass/fail per rule with specific findings

Example 6: Process review findings

code
User: "Let's go through the findings" (after a Review or Validate)
→ Invokes ProcessFindings workflow
→ Pipeline: presents finding N while committing fix for N-1
→ Medium-aware: proposes code fixes where prose was wrong medium
→ User decides per finding (apply, modify, skip, stop)