Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/orchestrate-chorus
Multi-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
Passed 17 of 21 test cases with the skill, and 4 of 21 without it.
and 24 more in the full report
15 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
During orchestrator coordination, different reviewer tools must be run at different quality gates. Map the three gates (proposal submitted, task submitted for verify, last task verified) to their exact corresponding reviewer names.
| Checked | Without skill | With skill |
|---|---|---|
| Maps proposal submission gate to proposal-reviewer-chorus | Missed | Passed |
| Maps task verification submission gate to task-reviewer-chorus | Missed | Passed |
| Maps last task verified gate to code-reviewer-chorus | Missed | Passed |
The instructions your model reads when the skill loads.
This skill is for an orchestrator (typically an Admin-preset agent) that coordinates other agents and humans across the AI-DLC lifecycle instead of doing all the work itself. The orchestrator decomposes work, hands each piece to a chosen owner, runs independent reviewers as quality gates, and gatekeeps the human-owned approval/verify gates — but never ships on its own.
Tool namespace under dsh. Bare tool names below (e.g.
chorus_pm_assign_idea) are the readable form; the actual callable name ismcp__chorus__-prefixed (mcp__chorus__chorus_pm_assign_idea). See the namespace note in the corechorusskill.
It complements the other skills rather than replacing them:
yolo-chorus — one agent drives the whole pipeline solo. Orchestration is the opposite: many agents, each owning a piece, coordinated by you.idea-chorus, proposal-chorus, develop-chorus, review-chorus, quick-dev-chorus — a single stage you execute yourself. Orchestration is the layer above those: you decide who runs each stage.Use it when more than one agent (or agent + human) will touch the work and someone has to keep them coherent:
Prerequisite: delegating ideas needs idea:admin; delegating tasks needs proposal:write. Run chorus_checkin() first to confirm your permission set.
chorus_pm_assign_idea (idea:admin)Hand a whole idea to a chosen agent or user. Parameters:
| Param | Meaning |
|---|---|
ideaUuid | The idea to delegate |
assigneeType | "agent" or "user" |
assigneeUuid | The chosen agent/user UUID (resolve names with chorus_search_mentionables) |
instanceUuid | (optional, agent targets only) pin the work to one durable AgentInstance — the (agent, host, cwd) place — so wakes land where the code lives |
Behavior you must understand:
test cases passed, vs 4 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.