chorus-orchestrate

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 chorus-orchestrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chorus-orchestrate
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/public/kiro-plugin/.kiro/skills/chorus-orchestrate
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-orchestrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple AI agents and humans on the same project creates ownership ambiguity, duplicate work, and unreviewed output. This Skill provides an orchestration playbook for delegating ideas and tasks to the right owners, running independent reviewers as quality gates, and enforcing human verification at every approval stage.

Core Features & Use Cases

  • Idea and Task Delegation: Assign ideas to agents or users with chorus_pm_assign_idea and distribute proposal tasks to developer agents with chorus_pm_assign_task, optionally pinning work to a specific agent instance.
  • Theme Decomposition: Break a container or epic idea into independent child ideas and fan each out to a distinct owner so they advance in parallel.
  • Adversarial Review Gates: Spawn read-only reviewer subagents (proposal, task, and code reviewers) that post VERDICT comments at each stage before work advances.
  • Use Case: A theme owner decomposes an epic into three child ideas, assigns one to Codex, one to a Claude dev agent, and one to a human, then gatekeeps each proposal and verify gate with independent reviewers.

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 chorus-orchestrate

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

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

Use chorus_pm_assign_idea with the idea UUID, assignee type (agent or user), and assignee UUID. Agent targets must hold idea:write permission, and you can optionally pin the work to a specific agent instance with instanceUuid.

How do I run multiple developer agents on one proposal?

After a proposal is approved, assign its unblocked tasks to several dev agents with chorus_pm_assign_task. As tasks reach done status, assign the next wave, respecting that only done unblocks downstream dependencies.

What permissions are needed to delegate ideas and tasks?

Delegating ideas requires idea:admin permission, and delegating tasks requires proposal:write. Run chorus_checkin first to confirm your permission set before attempting delegation.

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 the same feature that already has an approved proposal.

Can the orchestrator approve or merge work itself?

No. The orchestrator enforces Reversed-Conversation gates: it runs reviewers and hands approve, verify, and merge decisions to humans. Reviewer verdicts are advisory and never auto-approve or auto-verify work.