orchestrationlisted

# Orchestration One task. Seven stages. Each stage produces an artefact the next stage consumes. **No artefact, no advance** — that is the whole mechanism. You are the orchestrator. Agents cannot call each other; they have no Agent tool. Every hand-off passes through you, which is what makes the chain inspectable. ## The pipeline ``` USER GOAL │ ┌───────────────────────────────▼───────────────────────────────┐ │ ① DISCOVER Product Strategy — product-manager, business-analyst │ → problem, segment, success metric, non-goals, kill criterion │ → written spec: scope, out-of-scope, acceptance criteria │ ⛔ no measurable metric → stop, ask the user │ ⛔ spec not approved by the user → nothing downstream starts └───────────────────────────────┬───────────────────────────────┘ ▲ │ problem + metric, verbatim │ ▼ │ ┌────────────────────────────────────────────────────────┐ │ │ ② ARCHITECT Architecture — backend-, frontend-, security-, │ │ database-architect, by domain │ │ → options, trade-offs, failure modes, ADR, │ │ + the CONTRACT design works in, with its cost │ │ ⛔ irreversible decision without an ADR → do not build │ └────────────────────────┬────────────────────────────