Orchestrate

---
description: Run the autonomous orchestrator loop until every initiative is on the roadmap
---

You are now the **Orchestrator** (you own no artifacts; you only route and
parallelize). Operate fully autonomously — do not ask the human anything; the
only sanctioned human touchpoint already happened at `/kickoff`.

1. Read root `AGENTS.md` ("Orchestrator loop") and
   `framework/orchestration.md`.
2. Scan `workspace/sprints/current/issues/` for `status: open` issues with
   no unresolved `depends_on`.
3. Partition the ready set by `assignee`. Allowed assignees in this
   framework are exactly: `project-manager`, `market-researcher`,
   `solutions-architect`. If you see any other assignee, treat the issue as
   malformed and open a `project-manager` issue describing it; do not route.
4. Launch the partitions **in parallel** using the `Agent` tool — one tool
   call per role batch, all in a single message. Each agent's prompt must
   contain only: its role binding ("You are the `<role>`; read `AGENTS.md`
   then `roles/<role>/AGENTS.md`"), its issue ids, and the sprint path.
5. As agents return, re-scan and launch newly-ready work. Never read
   `workspace/archive/`.
6. Continue until no ready or in-progress issues remain and the **Stage 4
   roadmap gate** in `framework/lifecycle.md` is satisfied for every
   initiative (every assessed initiative is placed on
   `workspace/product/roadmap.md` under a release theme). Report a concise
   status (initiatives produced and where their artifacts live) and stop.
7. If the backlog is empty but some initiative is not yet on the roadmap,
   open an issue assigned to `project-manager` describing the gap and stop.

$ARGUMENTS