What problem does it solve? Moving a backend ticket from spec to merged code requires coordinating multiple specialized roles (architect, developer, reviewer, QA, publisher) with strict approval gates, isolated branches, and auditable handoffs. Doing this manually is error-prone and loses accountability between steps. ## Core Features & Use Cases - Orchestrated handoffs: Drives exactly one ticket through the architect → developer → code-review → qa → publish pipeline, requiring explicit developer approval before every dispatch. - Isolated Git workflow: Enforces issue branches and worktrees, never writes to protected or integration/* branches, and rechecks the base-commit gate before review and publish. - Evidence-based coordination: Each dispatched role records a model self-report against an immutable brief, emits heartbeats, and produces reports treated as evidence rather than authority to advance. - Use Case: A developer runs /implement on a ticket; the coordinator proposes an architect dispatch, waits for approval, then sequences developer, review, and QA dispatches, and finally offers /to-pull-requests after an accepted publish. ## Quick Start Ask the agent to implement a specific ticket using the backend-orchestration route, for example: "Run implement on ticket PROJ-123 and coordinate it through review and QA."
