develop

Manage developer task lifecycles and session attribution for Chorus-based pipelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges the gap between planning and implementation by giving developer agents a clear, auditable workflow to claim tasks, manage sessions, report progress, and submit work for verification so that work attribution, dependency enforcement, and handoffs are reliable.

Core Features & Use Cases

  • Task lifecycle management: claim, release, update status (in_progress, to_verify), and submit for verification.
  • Session-based attribution: checkin/checkout and sessionUuid propagation for sub-agent observability and audit trails.
  • Work reporting & acceptance criteria: structured work reports, self-check of acceptance criteria, and reviewer suggestions before admin verification.
  • Agent-team orchestration: integration with Claude Code Agent Teams for parallel sub-agents, wave-based DAG execution, and team lead orchestration.
  • Use case: a team lead spawns a Claude agent team to execute a feature in waves while Chorus enforces dependencies and aggregates session activity.

Quick Start

Claim a task, verify dependencies, start work and report progress with sessionUuid for sub-agents, then submit the task for verification when complete.

Frequently Asked Questions about develop

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

FAQPage Schema
How do I manage developer tasks and session workflows for AI agent teams?

You can manage developer tasks by claiming work, tracking sessionUuid for sub-agent observability, reporting progress, and submitting tasks for admin verification. This enforces dependencies and aggregates session activity for reliable work attribution.

How does session attribution work when spawning sub-agents in Claude Code?

Session attribution uses checkin and checkout processes with sessionUuid propagation to maintain sub-agent observability and audit trails. This ensures all work performed by parallel sub-agents is reliably tracked back to the correct developer session.

Can I enforce dependency execution for DAGs using Claude Code Agent Teams?

Yes, you can execute features in waves using Claude Code Agent Teams while the system enforces dependencies for DAGs. A team lead orchestrates parallel sub-agents, and the workflow validates task dependencies before execution proceeds.

What is the best way to report progress and submit work for admin verification?

The best way to report progress is by generating structured work reports that include self-checks of acceptance criteria and reviewer suggestions. Once complete, you submit the task for admin verification to close the loop.

Do I need a specific environment to run task lifecycle management for AI-driven development pipelines?

Task lifecycle management applies to Chorus-based projects where agents claim tasks, report work, and coordinate sessions. You need a Claude Code Agent Teams environment to fully utilize wave-based DAG execution and team lead orchestration.

Why does task coordination fail when parallel agents lack structured work reporting?

Task coordination fails without structured work reporting because dependency enforcement and work attribution become unreliable. Bridging planning and implementation requires auditable workflows to claim tasks, manage sessions, and submit verified work.