chorus-proposal

Creates Chorus proposals with document drafts, task drafts, and dependency DAGs for review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning an elaborated idea into an actionable plan requires coordinating PRDs, tech designs, and ordered task breakdowns across humans and agents. This Skill guides a PM agent through the Chorus Proposal workflow so drafts are created, validated, and submitted for Admin approval in a consistent, reviewable structure.

Core Features & Use Cases

  • Proposal lifecycle management: Create an empty proposal container, incrementally add document drafts (PRD, tech design, ADR, spec, guide) and task drafts, then validate and submit for Admin review.
  • Task dependency DAGs: Chain task drafts via draftUuid dependencies, batch-create tasks with intra-batch dependencies, and add or remove dependencies on existing tasks with cycle detection.
  • Feedback and revision loop: Handle reviewer FAIL verdicts or Admin rejections by self-rejecting the proposal back to draft status, revising drafts, and resubmitting.
  • Use Case: After an idea's elaboration is resolved, a PM agent creates a proposal containing a PRD and tech design, adds five module-scoped task drafts with acceptance criteria and dependencies, validates the proposal, and submits it so an Admin can approve it into real tasks for developer agents.

Quick Start

Ask the agent to create a Chorus proposal for the resolved idea, add a PRD and tech design draft, then add task drafts with acceptance criteria and dependencies before validating and submitting it for review.

Frequently Asked Questions about chorus-proposal

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

FAQPage Schema
How do I create a proposal in Chorus?

Call chorus_pm_create_proposal with the project UUID, title, description, and input idea UUIDs to create an empty container. Then incrementally add document drafts and task drafts, validate with chorus_pm_validate_proposal, and submit with chorus_pm_submit_proposal.

How do I add task dependencies in a Chorus proposal?

Each chorus_pm_add_task_draft call returns a draftUuid, which you pass in dependsOnDraftUuids of later drafts to build the DAG. After approval, use chorus_update_task with addDependsOn or removeDependsOn, which validates against cycles and self-dependencies.

Why was my Chorus task draft rejected?

Task drafts require acceptanceCriteriaItems with at least one non-blank description, or the call is rejected. The legacy acceptanceCriteria Markdown string does not satisfy this requirement, and each task may have at most six criteria items.

Can I edit a Chorus proposal after submitting it?

No, a proposal in pending status cannot be edited. You must reject it first with chorus_pm_reject_proposal to return it to draft status, revise the drafts, and then resubmit it for review.

Can a theme idea be used as proposal input in Chorus?

No, chorus_pm_create_proposal rejects any input idea with isContainer set to true. Derive a child idea from the theme and write the proposal against that child idea instead.