/project:plan#

Stage 3: Planning — Writes product briefs, PRD/technical specifications, and passes the BMAD Analysis Gate.

Triggers#

• When proceeding with product planning based on Specification artifacts
• When PRD, technical specifications, and BDD scenarios need to be written

Usage#

/project:plan
/project:plan --doc prd  " Community feature " 
 /project:plan --doc tech-spec

Options#

Prerequisites#

• Specification stage completed or skipped (check .pipeline/{slug}.yaml)
• Discovery/Specification artifacts auto-referenced if available

Execution Flow#

Phase 1: Product Brief#

Source: cc-bmad

1. Product brief writing (/bmad:product-brief)
   • Product overview based on Discovery/Specification artifacts
   • Goals, scope, constraints
   • Success criteria definition

Phase 2: Detailed Document Writing#

Source: cc-bmad, cc-pm-strategy

2. PRD or technical specification (/bmad:prd or /bmad:tech-spec)

   • Functional requirements detail
   • Non-functional requirements (performance, security, accessibility)
   • User flows
   • Data model draft

3. Business model (cc-pm-strategy: business-model)

   • Revenue model review
   • Cost structure analysis
   • Value proposition summary

Phase 3: Requirements Analysis#

Source: cc-bmad (Analyst persona)

4. Requirements analysis

   • Requirement clarity verification
   • Ambiguity and conflict identification
   • Priority assignment

5. BDD Acceptance Criteria

   • Gherkin format scenario writing
   • Given-When-Then structuring
   • Edge case scenarios included

Phase 4: Analysis Gate + Plan Quality Scoring#

BMAD Analysis Gate verification:

• Requirement clarity (requirement_clarity)
• Scope appropriateness (scope_appropriateness)
• Acceptance Criteria testability (ac_testability)

Plan Quality Scoring (see cc-bmad/references/phase-gates.md):

• Clarity ≥ 0.6 (weight 0.25)
• Completeness ≥ 0.6 (weight 0.25)
• Specificity ≥ 0.6 (weight 0.20)
• YAGNI Compliance ≥ 0.6 (weight 0.15)
• Scope Appropriateness ≥ 0.6 (weight 0.15)
• Weighted Total ≥ 0.8

Thresholds defined in cc-pipeline/config/thresholds.yaml. Documents are revised with feedback if gate or quality score fails.

Artifacts#

docs/prd-{slug}.md          # PRD (if selected)
docs/tech-spec-{slug}.md    # Technical specification (if selected)
docs/bdd-{slug}.md          # BDD scenarios

After Completion#

• Verify Analysis Gate passed
• Update .pipeline/{slug}.yaml state
• Present context-clear handoff:

✅ Planning stage complete (Analysis Gate PASSED). Artifacts saved:
  - docs/prd-{slug}.md
  - docs/tech-spec-{slug}.md
  - docs/bdd-{slug}.md

**Option 1 (Recommended)**: Clear context and continue to Design
  /clear
  Then run: /project:design

**Option 2**: Continue in current context
  Proceed directly to /project:design