Chorus-AIDLC/Chorus

Brainstorm runs an optional divergent-then-convergent dialogue to clarify a fuzzy idea before structured elaboration. Use it from the idea skill when a user has opted in to brainstorm mode; it asks one decision-point question at a time and synthesizes the answers into one elaboration round.

Brainstorm Chorus runs an optional divergent-then-convergent Q&A dialogue inside the idea skill to clarify fuzzy ideas before structured elaboration.

Chorus provides a work collaboration platform for AI agents and humans, covering the AI-DLC workflow from idea to done. Use it to check in, manage tasks and projects, and route to stage-specific skills.

Chorus is a work collaboration platform for AI Agents, enabling multiple Agents (PM, Developer, Admin) and humans to collaborate on the same platform. Use it to manage AI-DLC workflows from Idea to Done, with routing to stage-specific skills.

Chorus Blog Post writes bilingual (zh/en) release blog posts for the Chorus landing site, following a problem-first narrative and editorial style. Use it when announcing a new version or feature to craft posts that resonate with readers.

Chorus Code Reviewer reviews the aggregate code change behind a whole feature after every individual task passes, then posts a single structured VERDICT comment on the Idea. Use it as the final read-only adversarial gateway before an Idea's code ships in the AI-DLC pipeline.

Chorus Development guides developer agents through claiming tasks, reporting progress, self-checking acceptance criteria, and submitting work for verification in the Chorus AI-DLC workflow. Use it when working as a developer agent on a Chorus project task.

Chorus Docs routes questions about how to use, configure, deploy, or operate Chorus to the live documentation site at doc.chorus-ai.dev, grounding answers in current published docs instead of memory.

Chorus Orchestration coordinates multiple agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping approval gates. Use it when work decomposes into multiple owned pieces that need coherent coordination.

Chorus Proposal Reviewer audits PRD and task drafts against the originating Idea and posts a single structured VERDICT comment. Use it when reviewing Chorus proposals for completeness, specificity, dependencies, and integration checkpoints.

Chorus Task Reviewer fetches a Chorus task, its acceptance criteria, and proposal documents, then independently verifies the implementation and posts a structured VERDICT comment. Use it to review submitted work in an AI task management harness.

Code Reviewer performs the final ship-time review of a whole Chorus Idea, checking cross-task integration, architecture, security, regressions, and feature-level test coverage after all individual tasks pass. Use it after the last task of an idea is verified to post a VERDICT comment.

E2E Verification drives the running Chorus dev server in a real browser via Playwright MCP to confirm UI changes end-to-end. Use it when an acceptance criterion says the user sees X and only a real browser can confirm it.

Idea Chorus manages the ideation stage of the AI-DLC workflow, letting agents claim ideas, run structured elaboration rounds, and prepare for proposal creation.

OpenSpec Apply Change implements tasks from an OpenSpec change, guiding an agent through selecting a change, reading context files, and completing tasks one by one. Use when starting, continuing, or working through implementation tasks.

OpenSpec Archive Change archives a completed change in the experimental OpenSpec workflow. Use it to check artifact and task completion, optionally sync delta specs, and move the change to the archive.

OpenSpec Explore enters a thinking-partner mode for exploring ideas, investigating problems, and clarifying requirements before or during a change. It reads code, maps architecture, and compares options without implementing.

OpenSpec Propose creates a complete change proposal with design, specs, and tasks in one step. Use it when you want to quickly describe what to build and get artifacts ready for implementation.

PR Workflow guides an agent through creating a branch, committing changes, opening a pull request, fixing CI failures, and merging. Use it when code changes are ready to submit for review.

Plugin Maintenance guides modifying the Chorus plugin across Claude Code, Codex, OpenClaw, Kiro, Pi, and dsh ports, updating skill documentation, and releasing new plugin versions. Use it when changing skill content or publishing a new plugin release.

Proposal Chorus creates proposals with document drafts and task drafts, manages dependency DAGs, and validates and submits them for admin review in the Chorus AI-DLC planning workflow.

Quick Dev creates tasks directly without the full AI-DLC planning pipeline, for small, well-understood work like bug fixes, hotfixes, and small features. It guides agents through claiming, implementing, self-checking acceptance criteria, submitting, and getting independent review or admin verification.

Release walks through cutting a new version of Chorus, including version bump, changelog update, commit, pull request, tag, and GitHub release creation. Use it when you need to prepare and publish a software release following the project's checklist.

Review Chorus guides the Admin Agent through the AI-DLC review stage: approving or rejecting proposals, verifying completed tasks, and managing project governance.

Yolo Chorus drives a single prompt from Idea through Proposal, Execution, Verification, and Code Review to Done without human-in-the-loop. Use it when you want an agent to autonomously plan, build, review, and ship a software change in Chorus.