chorus-review

Approve proposals, verify tasks, and manage project governance in the Chorus AI-DLC workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-agent development pipelines stall without a human-proxy reviewer: proposals pile up unapproved, completed tasks sit unverified, and project governance drifts. This Skill gives an Admin Agent the full review workflow to keep the AI-DLC lifecycle moving.

Core Features & Use Cases

  • Proposal Review: Read full proposal drafts (PRD, tech design, task breakdowns), run an independent reviewer subagent, and approve or reject with actionable feedback.
  • Task Verification: Mark acceptance criteria as passed or failed, verify completed tasks, or reopen them for rework, then check which downstream tasks become unblocked.
  • Project Governance: Create projects and groups, close or delete ideas, tasks, and documents, and revoke approved proposals with full cascade cleanup.
  • Use Case: A PM Agent submits a proposal with a PRD and five task drafts. You spawn the chorus-proposal-reviewer subagent, read its VERDICT comment, approve the proposal, and immediately assign the materialized tasks to Developer Agents.

Quick Start

Ask the agent to check in with chorus_checkin, list pending proposals and tasks awaiting verification, then review and approve or reject each one.

Frequently Asked Questions about chorus-review

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

FAQPage Schema
How do I approve a proposal in the Chorus workflow?

Read the full proposal with chorus_get_proposal using section "full", review the document and task drafts against the quality checklist, then call chorus_admin_approve_proposal with a review note. Approval materializes the drafts into real documents and open tasks.

How do I verify a completed task in Chorus?

Review the task with chorus_get_task, mark each acceptance criterion with chorus_mark_acceptance_criteria, then call chorus_admin_verify_task to move it to done. If criteria fail, use chorus_admin_reopen_task to return it to in_progress with feedback.

What is the difference between rejecting and revoking a proposal?

Rejecting applies to pending proposals and returns them to draft status. Revoking applies to already-approved proposals and rolls back everything: materialized tasks are closed, documents are deleted, and the proposal returns to draft.

What happens when the reviewer subagent posts no VERDICT comment?

The reviewer exhausted its turn budget before posting. Respawn it once with instructions to batch MCP fetches and reserve turns for the VERDICT; if it fails again, review manually using the built-in quality checklists.

When should I close versus delete a task or idea?

Prefer closing, which preserves history and comments for future agents to read. Deletion is permanent and should be used sparingly, following the governance principle of close over delete.