proposal-chorus

Manage proposal containers with document drafts, task drafts, and dependency DAGs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating proposal creation, document drafting, and task planning across multiple stakeholders is time-consuming and error-prone. This Skill streamlines turning ideas into structured proposals that include PRDs, tech designs, and ordered task drafts so teams can move from planning to execution with fewer handoffs and clearer dependencies.

Core Features & Use Cases

  • Proposal lifecycle: create an empty proposal container, incrementally add or update document and task drafts, remove drafts, and review the current proposal state.
  • Task DAG management: express intra-proposal dependencies using draft UUIDs, batch-create tasks with intra-batch dependencies, and add/remove dependencies on existing tasks with cycle detection.
  • Validation and handoff: validate proposals to surface errors and warnings before submission, submit proposals to transition drafts to pending review, and support admin review and post-approval materialization of documents and tasks.
  • Use cases: convert one or more elaborated ideas into a single coordinated proposal, prepare PRD + tech design + implementation task DAG for developer agents, and enforce acceptance criteria and dependency ordering before work begins.

Quick Start

Create a new proposal by calling chorus_pm_create_proposal with the project UUID, title, description, and input idea UUIDs.

Frequently Asked Questions about proposal-chorus

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

FAQPage Schema
How do I create a proposal that links PRDs, tech designs, and task drafts?

You create a proposal container using your project UUID, title, description, and input idea UUIDs. This initializes a workspace to incrementally add document drafts like PRDs and tech designs alongside ordered task drafts.

What is a task dependency DAG and how does it help proposal drafting?

A task dependency DAG expresses intra-proposal execution order using task draft UUIDs. It ensures developer agents receive correctly sequenced implementation tasks, preventing execution bottlenecks by mapping prerequisites within the proposal.

How do I validate a proposal before submitting it for admin review?

You validate a proposal by running the validation operation to surface errors and dependency cycle warnings. This checks completeness and ordering before you transition drafts to pending review for admin approval.

Can I batch create tasks with intra-batch dependencies and check for cycles?

Yes, you can batch-create tasks with intra-batch dependencies using draft UUIDs. The system includes dependency cycle detection to automatically identify and prevent circular references when adding or removing task links.

What happens to document and task drafts after admin approval?

After admin approval, the proposal supports post-approval materialization of documents and tasks. This transitions validated drafts into actionable materials, triggering assignment hooks for developer agents to begin execution.

Does proposal drafting support removing existing task dependencies?

Yes, proposal drafting supports removing dependencies on existing tasks. The system provides deterministic operations for adding and removing dependencies while concurrently running cycle detection to maintain DAG integrity.