proposal-reviewer-chorus

Audits Chorus proposal drafts against the originating Idea and posts a structured VERDICT comment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LLM-written project proposals often look plausible but contain hidden gaps: missing requirements, vague acceptance criteria, wrong task dependencies, or hallucinated technical details. This Skill performs a read-only adversarial review of a submitted Chorus proposal and posts one structured verdict comment so a human admin can approve or reject with confidence.

Core Features & Use Cases

  • Adversarial draft audit: Fetches the proposal, its comments, the originating Idea, and its elaboration via Chorus MCP tools, then checks PRD completeness, specificity, feasibility, and hallucination risk.
  • Task DAG validation: Verifies task granularity, acceptance-criteria quality, requirement-to-AC coverage, dependency correctness, and the presence of an integration checkpoint in DAGs of 4+ tasks.
  • Structured verdict output: Classifies every finding as BLOCKER or NOTE and ends with exactly one machine-greppable verdict: VERDICT: PASS, VERDICT: PASS WITH NOTES, or VERDICT: FAIL.
  • Use Case: A PM agent submits a proposal for a new feature. Invoke this Skill with the proposal UUID; it cross-references the PRD and task drafts against the original Idea and posts a concise review comment the admin uses in the review-chorus workflow.

Quick Start

Ask the agent to review the Chorus proposal with a given proposal UUID and post its verdict comment on that proposal.

Frequently Asked Questions about proposal-reviewer-chorus

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

FAQPage Schema
How do I review a Chorus proposal with this skill?

Provide the proposal UUID and the skill fetches the full proposal, comments, originating Idea, and elaboration via Chorus MCP tools. It then audits document and task drafts and posts one structured review comment ending in a VERDICT line.

What verdicts can the proposal reviewer return?

Exactly three literal strings: VERDICT: PASS when no findings exist, VERDICT: PASS WITH NOTES when only non-blocking notes exist, and VERDICT: FAIL when any BLOCKER finding is present. Automation greps for these exact strings.

What is the difference between a BLOCKER and a NOTE finding?

A BLOCKER blocks implementation correctness, such as missing acceptance criteria, scope contradictions, wrong dependencies, or a missing integration checkpoint. A NOTE covers non-blocking issues like wording differences, pseudocode mismatches, or hallucination-risk specifics.

Can the proposal reviewer modify files or run commands?

No. The skill is strictly read-only: it cannot create, modify, or delete files, run shell commands, or install packages. Its only side effect is posting a single comment via chorus_add_comment.

How does round 2+ re-review work?

In round 2 and later, the reviewer only checks whether previous BLOCKERs were fixed, without introducing new NOTEs on unflagged areas. If all prior BLOCKERs are resolved, it posts VERDICT: PASS or PASS WITH NOTES.

When is an integration checkpoint required in a task DAG?

For any task DAG with four or more tasks, at least one task must be an integration checkpoint whose acceptance criteria require end-to-end execution of the preceding modules together. Its absence is classified as a BLOCKER.