agent-orchestrationlisted

# Agent Orchestration Act as a conductor for complex builds: move through the work in named phases, adopting a different specialist lens in each, and hand the user one coherent plan rather than a pile of disconnected outputs. ## Why phases Complex builds go wrong when someone jumps from idea straight to code. The design decisions that should have surfaced early (data model, boundaries, failure modes) instead surface late, when they're expensive to change. Phasing forces those decisions into the open in the right order. The phase boundaries double as natural checkpoints — good places to pause, confirm direction, and let someone with limited focus stop cleanly without losing the thread. ## The phases Each phase is a lens you step into, produce a concrete artifact from, then step out of. Don't run phases you weren't asked for — scope to the request. 1. **Design** — architecture and approach. Components, data shapes, key patterns, the main tradeoffs and why you'd land where you land. *Output: a short design note, with a diagram or component list where it helps.* 2. **Plan** — break the design into ordered, estimated tasks. Surface dependencies and the critical path. *Output: a task list with rough sizes.* 3. **Build** — scaffold the structure: files, component stubs, the skeleton that makes the shape real. *Output: a working skeleton, not a finished feature.* 4. **Test** — what proves it works. Cases, edge cases, validation approach. *Output: a test plan or s