orchestrate-chorus

Coordinate multiple agents and humans across the AI-DLC lifecycle by delegating ideas and tasks.

1.2k|104|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill orchestrate-chorus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrate-chorus
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/orchestrate-chorus
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill orchestrate-chorus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When more than one agent or human touches the same work, coordination breaks down: ideas lack a single accountable owner, parallel tasks collide on status transitions, and quality gates get skipped. This Skill gives an orchestrator agent a playbook for decomposing work, delegating each piece to a chosen owner, and enforcing the human-verify gates of the AI-DLC lifecycle.

Core Features & Use Cases

  • Idea and task delegation: Assign whole ideas via chorus_pm_assign_idea or individual tasks via chorus_pm_assign_task, optionally pinning work to a specific AgentInstance with instanceUuid.
  • Theme decomposition and fan-out: Derive child ideas from a container/theme idea and hand each child to a distinct owner (e.g., one to Codex, one to a Claude dev agent, one to a human) so they advance independently.
  • Independent adversarial review gates: Spawn read-only reviewer sub-agents (proposal, task, and code reviewers) that post VERDICT comments at each gate before work advances.
  • Use Case: You own a theme idea with three independent slices. Create three child ideas, assign each to a different agent, run the proposal reviewer when drafts arrive, and hand approve/verify decisions to the human owner at every gate.

Quick Start

Ask the orchestrator agent to decompose your theme idea into child ideas and assign each one to a different agent or human owner.

Frequently Asked Questions about orchestrate-chorus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate an idea to another agent in Chorus?▼

Use chorus_pm_assign_idea with the ideaUuid, assigneeType (agent or user), and assigneeUuid. The target agent must hold idea:write permission, and you need idea:admin. The assignee is woken and continues from the idea's current stage without re-claiming it.

How do I run multiple agents in parallel on one proposal?▼

After a proposal is approved, assign its currently unblocked tasks to several developer agents using chorus_pm_assign_task. As tasks reach done status, assign the next wave, respecting the DAG dependencies since only done unblocks downstream tasks.

What permissions are required to orchestrate agents in Chorus?▼

Delegating ideas requires idea:admin, and delegating tasks requires proposal:write. Run chorus_checkin first to confirm your permission set. Target agents must hold idea:write or task:write respectively, or the assignment call is rejected.

Can the orchestrator approve proposals or verify tasks itself?▼

No. The orchestrator enforces the Reversed-Conversation gates and never self-approves. It runs the independent reviewer, reads the VERDICT, then hands the approve, reject, or verify decision to the human owner, and never merges or pushes code.

When should I create a child idea instead of adding a task?▼

Create a child idea when the slice is genuinely separate scope needing its own elaboration, proposal, and owner. Add a task when the work is a discrete unit of an existing approved proposal. Assign directly when only the owner needs to change.