plan-pipeline-start

/plan-pipeline:start: 5-Phase Planning

Analyze the request and produce a complete implementation plan through structured phases. No code is written. Every significant decision is recorded. Run /clear after this command before running /plan-pipeline:validate.

---

Phase 1: PRD & Design Analysis

Step 1.1: PRD Analysis

Skip if no PRD exists (refactor, infra change, bug fix).

Read all PRD files and docs/INFORMATION_ARCHITECTURE.md if present. Scan the codebase to understand current implementation status.

Surface findings in 3 buckets:

Missing requirements: acceptance criteria that are absent or incomplete Ambiguous requirements: items with multiple valid interpretations Compliance concerns: security, data privacy, API contract implications

For each finding: present options with concrete pros/cons. Discuss with user. Record every decision in the plan file under a ## Decisions section before moving on. Do not proceed past unresolved ambiguities.

Step 1.2: Design Analysis

Skip if no UI changes are in scope.

Read: DESIGN_SYSTEM.md, existing UX ADRs, CLAUDE.md UX rules.

Produce specs for:

• Screen inventory: new/modified screens, route placement, component reuse audit
• State catalog: empty, loading, populated, error, and partial states for every interactive element
• Interaction specs: user flows (happy path + alternates), focus/keyboard behavior
• Animation specs: map each interaction to existing keyframes or specify new ones, include prefers-reduced-motion fallbacks
• Responsive behavior: breakpoints, web/mobile divergence decisions
• Accessibility: WAI-ARIA pattern selection, live regions, error visibility

Create Design ADRs for significant UX decisions (choice of interaction pattern, new animation convention, platform divergence). Record minor layout choices directly in the plan file.

---

Phase 2: Technical Analysis

Spawn 1-2 Explore agents for targeted codebase research. Run them in the background via Task tool.

While agents run, check:

• Existing ADRs in docs/adr/: if 3+ ADRs confirm a decision → auto-resolve without asking
• PATTERNS.md: apply confirmed patterns directly

When agents return: present architecture decisions with 2-3 options each, concrete pros/cons, and a recommendation. Ask for user input on each unresolved decision.

For each significant decision:

1. Create docs/adr/ADR-XXXX.md using standard Nygard format (Context / Decision / Status / Consequences)
2. Update docs/adr/PATTERNS.md with the new observation

---

Phase 3: Scope Assessment

Apply trigger rules to determine which research agents are needed. Present the proposed team with justification for each inclusion.

Research agent pool:

Tier labels (descriptive, not prescriptive):

• Tier 0 (0 agents): Solo (inline research, no spawning)
• Tier 1 (1-3 agents): Focused
• Tier 2 (4-6 agents): Standard
• Tier 3 (7-9 agents): Comprehensive
• Tier 4 (10+ agents): Full Spectrum

Tell the user: "I recommend a [Tier N - Label] team: [agent list with one-line justification each]. Want to add or remove any agents?"

Wait for approval before Phase 4.

---

Phase 4: Research & Plan Creation

Tier 0: Conduct inline research. Write plan directly without spawning agents.

Tier 1+: Spawn approved agents in parallel using Task tool (run_in_background: true). For each agent, provide:

• Its specific research scope
• The relevant files/areas to investigate
• The questions it needs to answer

Monitor agents by reading their output files directly (TaskOutput is deprecated since v2.1.83; use Read on .claude/tasks/<id>/output.log instead). Report progress: "3/6 agents complete..."

When all agents return: if planning-coordinator was spawned, send it all agent reports and have it synthesize the final plan. Otherwise, synthesize directly.

Plan file structure (docs/plans/plan-{name}.md):

# Plan: {feature-name}
Created: {date} | Branch: {branch-name} | Tier: {N}

## Summary
One paragraph: what this implements and why.

## Decisions
Decisions recorded during Phase 1 (PRD analysis).

## Architecture
ADRs created, patterns applied, architectural choices made.

## Tasks
Ordered task list with layers (1 = foundation, 2 = depends on 1, etc.)

### Layer 1
- [ ] Task A: description, files affected, acceptance criteria
- [ ] Task B: description, files affected, acceptance criteria

### Layer 2
- [ ] Task C (depends on A): description, files affected, acceptance criteria

## Test Plan
How each task will be verified. TDD tasks marked explicitly.

## Integration Verification
Smoke test commands to run post-execution (if backend/services in scope).

## Out of Scope
What this plan explicitly does not address.

Commit: plan file + ADR files + agent report manifests.

---

Phase 5: Finalize Metrics

Record timestamps, phase durations, agent counts, and cost estimates in docs/plans/metrics/{name}.json. Commit.

---

Auto-Transition

If Phase 1 produced no unresolved ambiguities and Phase 2 produced no unresolved decisions: auto-start /plan-pipeline:validate without asking.

If any human discussion occurred: ask "Ready to validate this plan?" before proceeding.

---

Usage

/plan-pipeline:start

Provide the feature description or point to a PRD file when prompted. The command handles the rest interactively.

When to Use

Use for any non-trivial feature: anything touching more than 2 files, involving architecture decisions, or where a planning mistake would be expensive to undo.

For simple changes (typos, trivial refactors): use /plan mode instead.

Pipeline Position

/plan-pipeline:ceo-review    → product direction locked
/plan-pipeline:eng-review    → architecture locked
/plan-pipeline:start         → produce implementation plan   ← you are here
/plan-pipeline:validate      → validate before execution
/plan-pipeline:execute       → execute to merged PR