chorus-develop

Claims Chorus tasks, reports work progress, and orchestrates parallel Kiro subagent execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating AI coding agents across a multi-task development pipeline is chaotic: tasks get lost, progress goes unreported, dependencies break, and parallel agents work without observability. This Skill gives developer agents a structured workflow to claim tasks, execute work, self-check acceptance criteria, and submit for human verification within the Chorus AI-DLC platform.

Core Features & Use Cases

  • Full Task Lifecycle Management: Claim, start, report, self-check acceptance criteria, and submit tasks for admin verification using Chorus MCP tools.
  • Parallel Subagent Orchestration: Spawn up to 4 concurrent Kiro subagents with session-based observability, wave-based DAG dependency resolution, and per-session attribution.
  • Review Gateway Integration: Trigger independent task-reviewer and code-reviewer subagents that post VERDICT comments before work ships.
  • Use Case: A PM agent creates a proposal with 8 tasks in a dependency DAG. The main agent spawns subagents wave by wave, each claiming tasks, reporting commits and PRs, self-checking acceptance criteria, and submitting for verification until the idea ships.

Quick Start

Ask the agent to check in with Chorus, list available tasks for the project, claim the highest-priority unblocked task, and start development following the chorus-develop workflow.

Frequently Asked Questions about chorus-develop

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

FAQPage Schema
How do I claim and execute a Chorus task as a developer agent?

Call chorus_get_available_tasks to find work, review it with chorus_get_task, then claim it via chorus_claim_task. Set status to in_progress with chorus_update_task, do the work, report with chorus_report_work, self-check acceptance criteria, and submit via chorus_submit_for_verify.

How do I run multiple coding tasks in parallel with Kiro subagents?

Use wave-based execution: call chorus_get_unblocked_tasks, spawn up to 4 subagents each with a task UUID and sessionUuid, wait for to_verify status, verify tasks to done, then fetch the next wave. Only done or closed tasks unblock downstream dependencies.

Why was my task rejected when setting status to in_progress?

Chorus enforces dependencies server-side: chorus_update_task rejects the transition if any dependsOn task is not done or closed. Use chorus_get_unblocked_tasks to find tasks you can start immediately.

Does a subagent need a session to work on Chorus tasks?

Yes. Subagents must call chorus_session_checkin_task before starting, pass sessionUuid to chorus_update_task and chorus_report_work for attribution, and call chorus_session_checkout_task when done. The main agent skips sessions entirely.

What happens after I submit a task for verification?

The main agent spawns a chorus-task-reviewer subagent that posts a VERDICT comment on the task. PASS proceeds to admin verification; FAIL lists blockers you must fix before resubmitting. The to_verify status does not unblock dependent tasks.

Why is my subagent's session not visible in the Chorus UI?

Sessions with no activity for one hour are hidden from default lists but still exist. Reach them via chorus_list_sessions or chorus_get_session, and send a heartbeat or any session-touching tool call to make the session visible again.