/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