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 on Hermes. Invoked from the idea skill as a prelude to structured elaboration; asks one question at a time (in chat, or as single-question elaboration rounds when no human is in chat), produces one ElaborationRound of decision-point Q&A and returns control.…
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…
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.
Read-only Chorus code-review gateway for Hermes — the final ship-time review of an Idea's aggregate code change (the whole feature across all its tasks, not one task). Runs as a delegatetask child whose context starts with [chorus-reviewer:code]; fetches the Idea, its approved proposals, documents, and tasks via MCP…
Read-only Chorus proposal reviewer for Hermes. Runs as a delegatetask child whose context starts with [chorus-reviewer:proposal]; fetches a proposal via MCP, audits PRD/task drafts against the originating Idea, and posts exactly one structured VERDICT comment on the proposal.
Read-only Chorus task reviewer for Hermes. Runs as a delegatetask child whose context starts with [chorus-reviewer:task]; fetches a task, its acceptance criteria, and the originating proposal documents via MCP, verifies the implementation from the source files and the parent-built evidence bundle, and posts exactly…
Optional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the chorus-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 resolves elaboration.
OpenSpec-mode authoring for Chorus PM workflows in Kiro CLI. 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 (bash chorus-api.sh wrapper as…
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.
Lightweight, Chorus-native local specs for Chorus PM workflows on dsh — a durable local spec .chorus/specs/ /spec.md (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort .chorus/specs/ / - / holding Chorus-typed docs (prd.md, techdesign.md…
Lightweight, Chorus-native local specs for Chorus PM workflows in Hermes — a durable local spec .chorus/specs/ /spec.md (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort .chorus/specs/ / - / holding Chorus-typed docs (prd.md…
Lightweight, Chorus-native local specs for Chorus PM workflows in Kiro CLI — a durable local spec .chorus/specs/ /spec.md (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort .chorus/specs/ / - / holding Chorus-typed docs (prd.md…
Bounded factual research for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
Bounded factual research (Hermes) for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
Bounded factual research for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
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: