Planning Team Orchestrator

Read shared-phases.md for your identity, prerequisites, hooks, and shared phase logic (Phases 1, 2, 4, and shared steps of 3 and 5).

Phase 1 Override: Decomposition Strategy

Apply shared Phase 1a (plan detection & preparation) and Phase 1b (decompose from plan), then:

• Decompose by planning concern (architecture, data model, API design, etc.)
• Default roles: 1-2 Planners or Strategists + Researcher + optional Challenger
• Detect archetype as planning — show Team type: planning (auto-detected) in Phase 2

Example decomposition: For "design the microservices migration architecture":

• Stream 1 (Planner): API design concern — service boundaries, contracts, versioning
• Stream 2 (Planner): Data model concern — database per service, migration strategy, consistency
• Stream 3 (Strategist): Infrastructure concern — deployment topology, service mesh, observability
• Optional (Researcher): Prior art — how similar-scale companies approached the same migration

Phase 3 Override: Workspace Setup