The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle)
About the project
Chorus is a coordination harness for teams of coding agents and humans, combining agent orchestration, task tracking, permissions, observability, and recovery in one workflow. It is for collaborative software development where agents propose changes and people verify them before delivery, and the catalogue entries provide its skills, hooks, agents, commands, MCP integration, plugin, and configuration.
Optional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never validates elaboration.
How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp. A concise shared reference for any flow that drives Chorus from the shell.
Final ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read the integrated code, check cross-task integration / architecture / security / regression / coverage, run tests. Invoke after the last task of an idea-rooted proposal is verified; ends with a VERDICT…
OpenSpec-mode authoring for Chorus PM workflows on dsh — the default whenever OpenSpec is usable. Consumes the ## Spec Mode block the chorus-dsh bundle injects (mode resolved once at load by src/spec-mode.ts), scaffolds openspec/changes/ / on disk, and mirrors Markdown files into Chorus document drafts via chorus mcp…
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.
Adversarial read-only review of a submitted Chorus proposal — document completeness, task granularity, AC↔requirement coverage, and the dependency DAG. Invoke after a proposal is submitted; ends with a VERDICT comment.
Adversarial verification of a submitted Chorus task against its AC and proposal documents — read the code, verify each criterion, run tests. Invoke after a task is submitted for verify; ends with a VERDICT comment.
Chorus documentation router for Hermes Agent — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
Chorus Idea workflow on Hermes — claim ideas, run elaboration rounds (asked in chat, or via @mention when Chorus wakes the gateway), and prepare for proposal creation.
OpenSpec-mode authoring for Chorus PM workflows in Hermes. The default whenever OpenSpec is usable; consumes the resolved ## Spec Mode (never re-detects). Scaffolds openspec/changes/ / on disk, and mirrors Markdown files into Chorus document drafts via chorus mcp call --arg-file (the native Chorus MCP tool as fallback…
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.
Chorus Proposal workflow on Hermes — create proposals with document and task drafts, manage dependency DAG, validate, submit, and run the read-only proposal reviewer via delegatetask.
Full-auto AI-DLC pipeline in Hermes — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle, with delegatetask wave execution and read-only delegatetask reviewers.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: