claude-orchestratelisted

Asserts the orchestrator role for the current session, holds the build loop and the queue-refill sweep, and dispatches to the feature, review, and worktree skills. Use when asked to "be the orchestrator", "run the orchestrator", "orchestrate this project", or to set up the control session for parallel feature builds. Do NOT build features or merge PRs in this session.
erclx/aitk · ★ 2 · AI & Automation · score 71

Install: claude install-skill erclx/aitk

# Claude orchestrate This session is the orchestrator: the one warm session that holds the cross-feature picture. It plans and reviews. It does not build, and it does not merge. Building happens in cold worker sessions the human launches. Merging is the human's gate. This skill holds the framing, the board procedure, and the dispatch. Every step that builds something runs an existing skill. The queue rules below decide which one runs and when. Run `aitk docs operating-model` for the model this skill enacts: the two roles and what each owns, the loop end to end, why the worker's self-review and this session's review are different passes, and how a feature is sized. ## On invocation Read the board in parallel, resolving the paths at the main worktree root per Worktrees in `CLAUDE.md`: - `.claude/tasks/priority.md`: execution order and what each task is waiting on - `.claude/tasks/index.md`: what is queued - `.claude/plans/*.md`: features already planned and ready to hand off - `.claude/ROADMAP.md`: sequencing rationale, when the file exists - open PRs via `gh pr list --json number,title,headRefName,isDraft` Then output the state of play so the human knows what to launch, review, and merge. `priority.md` is the ordering source. `index.md` sorts by filename and says nothing about order, so read the sequence from the first and never infer it from the second. When `priority.md` is absent, report the queue and say the order is unrecorded. The roadmap is optional and this s