yolo-chorus

Automates the full AI-DLC pipeline from prompt through proposal, execution, and verification to done.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a feature from a raw idea through planning, review, implementation, and verification normally requires constant human orchestration across many steps. This Skill drives the entire Chorus AI-DLC lifecycle autonomously from a single natural-language prompt, with no interactive prompts unless the pipeline gets stuck.

Core Features & Use Cases

  • End-to-End Pipeline Automation: Creates the project and Idea, runs self-elaboration, drafts a Proposal with a tech-design document and task DAG, then executes tasks in dependency-ordered waves.
  • Adversarial Review Loops: Runs independent proposal, task, and whole-feature code reviews via read-only sub-agents (with inline single-agent fallbacks), looping on FAIL verdicts up to configurable round limits.
  • Use Case: Give it a detailed prompt like "build a REST API for team expense tracking with approval workflows" and it produces a verified, code-reviewed implementation with a mandatory Idea Completion Report, escalating only genuinely blocked items to a human.

Quick Start

Ask the agent to run the yolo skill with a detailed natural-language description of the feature you want built, optionally including an existing project UUID or name to reuse.

Frequently Asked Questions about yolo-chorus

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

FAQPage Schema
How do I run a fully automated AI-DLC pipeline from one prompt?

Invoke the yolo skill with a detailed natural-language description of what to build. It creates the project and Idea, self-elaborates, drafts and submits a Proposal, executes tasks in dependency waves, and verifies everything through adversarial review loops without interactive prompts.

What permissions does the Chorus API key need for yolo mode?

The key needs idea:write, proposal:write and admin, task:write and admin, and project:write. An Admin-preset key with all 15 permissions satisfies this; the skill runs a preflight check and aborts listing every missing resource:action pair.

Can yolo-chorus work without sub-agent support in my harness?

Yes. Every review step has an inline self-review fallback where the main agent follows the reviewer skill itself, and execution falls back to sequential main-agent task processing. The pipeline completes the same way, just without parallelism.

What happens when a task or proposal keeps failing review?

Each loop is bounded: proposal review, task review, and code review default to 3 rounds. A stuck task is escalated for human intervention without halting the pipeline, while a stuck proposal or code-review gateway stops the run with an escalation report.

When should I use quick-dev instead of the yolo pipeline?

Use quick-dev-chorus for small, single-step work where the Idea-to-Proposal overhead is unnecessary. Yolo is intended for full features that benefit from elaboration, a tech-design document, a task DAG, and multi-stage review.