chorus-aidlc
- 121 skills
- 0 followers
- 1.2k repo stars
- yesterday last updated
- ▌ Proposal Reviewer Chorus 2 · chorus-aidlcAdversarial read-only review of a submitted Chorus proposal — document completeness, task granularity, AC↔requirement coverage, and the dependency DAG. Invoke after a proposal is submitted; ends with a VERDICT comment.
- ▌ Chorus CLI 3 · chorus-aidlcHow to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any flow that drives Chorus from the shell.
- ▌ Docs 4 · chorus-aidlcChorus documentation router — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Brainstorm 3 · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
- ▌ Brainstorm 4 · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
- ▌ Research · chorus-aidlcBounded factual research for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
- ▌ Docs 5 · chorus-aidlcChorus documentation router for Hermes Agent — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Idea 5 · chorus-aidlcChorus Idea workflow on Hermes — claim ideas, run elaboration rounds (asked in chat, or via @mention when Chorus wakes the gateway), and prepare for proposal creation.
- ▌ Yolo 5 · chorus-aidlcFull-auto AI-DLC pipeline in Hermes — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle, with delegate_task wave execution and read-only delegate_task reviewers.
- ▌ Research Chorus 2 · chorus-aidlcBounded factual research for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
- ▌ Chorus 7 · chorus-aidlcChorus AI Agent collaboration platform for Hermes Agent — overview, common tools, Hermes setup, and routing to stage-specific skills.
- ▌ Review 5 · chorus-aidlcChorus Review workflow — approve/reject proposals, verify tasks, run read-only reviewers via Hermes delegate_task, and manage project governance.
- ▌ Develop 5 · chorus-aidlcChorus Development workflow — claim tasks, report work, manage sessions, and run parallel workers with Hermes delegate_task.
- ▌ Proposal 5 · chorus-aidlcChorus Proposal workflow on Hermes — create proposals with document and task drafts, manage dependency DAG, validate, submit, and run the read-only proposal reviewer via delegate_task.
- ▌ Research 2 · chorus-aidlcBounded factual research (Hermes) for Chorus Idea clarification, Proposal design, or an explicit pre-development Tracker Research request. Returns evidence and unknowns to the calling workflow.
- ▌ Quick Dev 5 · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, run the task reviewer via Hermes delegate_task, and verify.
- ▌ Spec Lite 5 · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows in Hermes — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Brainstorm 5 · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas on Hermes. Invoked from the idea skill as a prelude to structured elaboration; asks one question at a time (in chat, or as single-question elaboration rounds when no human is in chat), produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts summary or transcript comments, never resolves elaboration.
- ▌ Chorus CLI 4 · chorus-aidlcHow to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any Hermes flow that drives Chorus from the shell (via `terminal`).
- ▌ Orchestrate 5 · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Openspec Aware 5 · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows in Hermes. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (the native Chorus MCP tool as fallback when the `chorus` CLI is missing). Required reading for the proposal, develop, and yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).
- ▌ Chorus Code Reviewer 2 · chorus-aidlcRead-only Chorus code-review gateway for Hermes — the final ship-time review of an Idea's aggregate code change (the whole feature across all its tasks, not one task). Runs as a delegate_task child whose context starts with [chorus-reviewer:code]; fetches the Idea, its approved proposals, documents, proposal tasks and linked Quick Tasks via MCP, reviews the aggregate implementation from the source files and the parent-built evidence bundle, and posts exactly one structured VERDICT comment on the Idea.
- ▌ Chorus Task Reviewer 2 · chorus-aidlcRead-only Chorus task reviewer for Hermes. Runs as a delegate_task child whose context starts with [chorus-reviewer:task]; fetches a task, its acceptance criteria, and the originating proposal documents via MCP, verifies the implementation from the source files and the parent-built evidence bundle, and posts exactly one structured VERDICT comment on the task.
- ▌ Chorus Proposal Reviewer 2 · chorus-aidlcRead-only Chorus proposal reviewer for Hermes. Runs as a delegate_task child whose context starts with [chorus-reviewer:proposal]; fetches a proposal via MCP, audits PRD/task drafts against the originating Idea, and posts exactly one structured VERDICT comment on the proposal.
- ▌ Proposal 3 · chorus-aidlc bundleChorus Proposal workflow — create proposals with document and task drafts, manage dependency DAG, validate and submit for review.
- ▌ Chorus CLI 2 · chorus-aidlcHow to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any flow that drives Chorus from the shell.
- ▌ Orchestrate 2 · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Quick Dev 3 · chorus-aidlc bundleQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Spec Lite 3 · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Docs Chorus 2 · chorus-aidlcChorus documentation router — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Idea Chorus 2 · chorus-aidlcChorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
- ▌ Yolo Chorus 2 · chorus-aidlcFull-auto AI-DLC pipeline — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle.
- ▌ Chorus 6 · chorus-aidlcChorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
- ▌ Review 4 · chorus-aidlcChorus Review workflow — approve/reject proposals, verify tasks, and manage project governance.
- ▌ Develop 4 · chorus-aidlcChorus Development workflow — claim tasks, report work, manage sessions, and run wave-based execution on OpenClaw.
- ▌ Orchestrate 3 · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Review Chorus 2 · chorus-aidlcChorus Review workflow — approve/reject proposals, verify tasks, and manage project governance.
- ▌ Openspec Aware 2 · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows in Pi. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-mcp-call.sh` wrapper as fallback). Required reading for the proposal, develop, and yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).
- ▌ Proposal 4 · chorus-aidlcChorus Proposal workflow — create proposals with document and task drafts, manage dependency DAG, validate and submit for review.
- ▌ Develop Chorus 2 · chorus-aidlcChorus Development workflow — claim tasks, report work, manage sessions, and run wave-based execution on dsh.
- ▌ Quick Dev 4 · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Spec Lite 4 · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows on OpenClaw — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Proposal Chorus 2 · chorus-aidlcChorus Proposal workflow — create proposals with document and task drafts, manage dependency DAG, validate and submit for review.
- ▌ Brainstorm 2 · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never validates elaboration.
- ▌ Openspec Aware 3 · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows in Claude Code. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-api.sh` wrapper as fallback). Required reading for the proposal, develop, and yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).
- ▌ Quick Dev Chorus 2 · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Orchestrate 4 · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Brainstorm Chorus 2 · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never validates elaboration.
- ▌ Orchestrate Chorus 2 · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Openspec Aware 4 · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows on OpenClaw — the default whenever OpenSpec is usable. Resolves the whole spec-mode contract (lite/openspec/off) by sourcing the plugin's shipped `bin/resolve-spec-mode.sh` (no SessionStart hook on OpenClaw), scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-api.sh` wrapper as fallback). When OpenSpec isn't usable the mode resolves to spec-lite (see the spec-lite skill). Required reading for the proposal, develop, and yolo skills.
- ▌ Code Reviewer Chorus 2 · chorus-aidlcFinal ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read the integrated code, check cross-task integration / architecture / security / regression / coverage, run tests. Invoke after the last task of an idea-rooted proposal (or the last Quick Task linked to the Idea) is verified; ends with a VERDICT comment on the Idea.
- ▌ Task Reviewer Chorus 2 · chorus-aidlcAdversarial verification of a submitted Chorus task against its AC and proposal documents — read the code, verify each criterion, run tests. Invoke after a task is submitted for verify; ends with a VERDICT comment.
- ▌ Openspec Aware Chorus · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows on dsh — the default whenever OpenSpec is usable. Consumes the `## Spec Mode` block the chorus-dsh bundle injects (mode resolved once at load by `src/spec-mode.ts`), scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (package-local `chorus-mcp-call.mjs` wrapper as fallback). When OpenSpec isn't usable the mode resolves to spec-lite (see `spec-lite-chorus`). Required reading for the proposal, develop, and yolo skills.
- ▌ Chorus Quick Dev · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Chorus Spec Lite · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows in Kiro CLI — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier chorus-openspec-aware path. Read from chorus-proposal / chorus-develop / chorus-yolo when the spec mode resolves to `lite`.
- ▌ Proposal Reviewer · chorus-aidlcAdversarial read-only review of a submitted Chorus proposal — document completeness, task granularity, AC↔requirement coverage, and the dependency DAG. Invoke after a proposal is submitted; ends with a VERDICT comment.
- ▌ Chorus Brainstorm · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the chorus-idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
- ▌ Chorus Orchestrate · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Chorus Openspec Aware · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows in Kiro CLI. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-api.sh` wrapper as fallback). Required reading for the chorus-proposal, chorus-develop, and chorus-yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).
- ▌ Chorus 2 · chorus-aidlcChorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills. (Codex port)
- ▌ Docs 2 · chorus-aidlcChorus documentation router — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Idea 2 · chorus-aidlcChorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
- ▌ Yolo 2 · chorus-aidlcFull-auto AI-DLC pipeline — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle.
- ▌ Chorus 3 · chorus-aidlcChorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
- ▌ Review 2 · chorus-aidlcChorus Review workflow — approve/reject proposals, verify tasks, and manage project governance.
- ▌ Docs 3 · chorus-aidlcChorus documentation router — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Idea 3 · chorus-aidlc bundleChorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
- ▌ Yolo 3 · chorus-aidlc bundleFull-auto AI-DLC pipeline — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle.
- ▌ Chorus 4 · chorus-aidlcChorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
- ▌ Develop 2 · chorus-aidlcChorus Development workflow — claim tasks, report work, manage sessions, and integrate with Pi subagents.
- ▌ Proposal 2 · chorus-aidlcChorus Proposal workflow — create proposals with document and task drafts, manage dependency DAG, validate and submit for review.
- ▌ Chorus 5 · chorus-aidlc bundleChorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
- ▌ Review 3 · chorus-aidlc bundleChorus Review workflow — approve/reject proposals, verify tasks, and manage project governance.
- ▌ Quick Dev 2 · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Spec Lite 2 · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows in Pi — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Develop 3 · chorus-aidlc bundleChorus Development workflow — claim tasks, report work, manage sessions, and integrate with Claude Code Agent Teams.
- ▌ Idea 4 · chorus-aidlcChorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
- ▌ Yolo 4 · chorus-aidlcFull-auto AI-DLC pipeline — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle.
- ▌ Quick Dev Chorus · chorus-aidlc bundleQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Proposal · chorus-aidlcChorus Proposal workflow — create proposals with document and task drafts, manage dependency DAG, validate and submit for review.
- ▌ Brainstorm Chorus · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
- ▌ E2e Verification · chorus-aidlcUse when manually verifying a Chorus frontend change in a real browser — finding local login credentials, driving the running dev server with the Playwright MCP, logging in, navigating to a page, and capturing snapshots/screenshots for e2e acceptance.
- ▌ Quick Dev · chorus-aidlcQuick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
- ▌ Spec Lite · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Orchestrate Chorus · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates.
- ▌ Chorus CLI · chorus-aidlcHow to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any flow that drives Chorus from the shell.
- ▌ Plugin Maintenance · chorus-aidlcGuide for modifying the Chorus plugin (Claude Code, Codex/TRAE CLI, OpenClaw, Kiro, Pi, dsh, and Hermes ports), updating skill documentation, and releasing new plugin versions.
- ▌ Orchestrate · chorus-aidlcMulti-agent orchestration playbook — coordinate OTHER agents and humans across the AI-DLC lifecycle by delegating ideas and tasks, running independent reviewers, and gatekeeping at the Reversed-Conversation gates. (Codex port)
- ▌ Code Reviewer Chorus · chorus-aidlcRead-only adversarial Chorus code-review gateway — independently reviews an Idea's aggregate code change (the whole feature across all its tasks) and posts a single structured VERDICT comment on the Idea.
- ▌ Task Reviewer Chorus · chorus-aidlcRead-only adversarial Chorus task reviewer — independently verifies an implementation against its acceptance criteria and posts a single structured VERDICT comment.
- ▌ Brainstorm · chorus-aidlcOptional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
- ▌ Openspec Aware · chorus-aidlcOpenSpec-mode authoring for Chorus PM workflows in Codex. The default whenever OpenSpec is usable; consumes the resolved `## Spec Mode` (never re-detects). Scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via `chorus mcp call --arg-file` (bash `chorus-mcp-call.sh` wrapper as fallback). Required reading for the proposal, develop, and yolo skills. When OpenSpec is not the resolved mode, this skill no-ops and the caller follows the resolved mode (spec-lite or free-form).
- ▌ Proposal Reviewer Chorus · chorus-aidlcRead-only adversarial Chorus proposal reviewer — audits PRD/task drafts against the originating Idea and posts a single structured VERDICT comment.
- ▌ Chorus Code Reviewer · chorus-aidlcRead-only Chorus code-review gateway — the final ship-time review of an Idea's aggregate code change (the whole feature across all its tasks, not one task). Fetches the Idea, its approved proposals, documents, proposal tasks and linked Quick Tasks via MCP, reviews the aggregate implementation, and posts a structured VERDICT comment on the Idea. Invoke with spawn_agent({items:[{type:"skill", path:"chorus:chorus-code-reviewer"}, {type:"text", text:"Review the code for idea <idea-uuid>. Round: N. Post VERDICT."}]}).
- ▌ Chorus Task Reviewer · chorus-aidlc bundleRead-only Chorus task reviewer. Fetches a task plus its acceptance criteria plus originating proposal documents via MCP, independently verifies the implementation, and posts a structured VERDICT comment. Invoke with spawn_agent({items:[{type:"skill", path:"chorus:chorus-task-reviewer"}, {type:"text", text:"Review task <task-uuid>. Max review rounds: 3. Post VERDICT."}]}).
- ▌ Spec Lite Chorus · chorus-aidlcLightweight, Chorus-native local specs for Chorus PM workflows on dsh — a durable local spec `.chorus/specs/<slug>/spec.md` (one per capability/feature) edited in place and NEVER synced (git history is its record), plus one dated folder per change effort `.chorus/specs/<slug>/<YYYY-MM-DD>-<change-slug>/` holding Chorus-typed docs (prd.md, tech_design.md, …) that ARE mirrored 1:1 into persistent Chorus Documents via `--arg-file`. The fallback when OpenSpec isn't in use; a low-token alternative to the heavier openspec-aware-chorus path. Read from proposal / develop / yolo when the spec mode resolves to `lite`.
- ▌ Chorus Docs · chorus-aidlcChorus documentation router — consult the live Chorus docs site to answer product-usage questions (UI workflow, agent/plugin setup, API/MCP, deployment, operations).
- ▌ Chorus Idea · chorus-aidlcChorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
- ▌ Chorus Yolo · chorus-aidlcFull-auto AI-DLC pipeline — from prompt to done. Automates the entire Idea -> Proposal -> Execute -> Verify lifecycle.
- ▌ Code Reviewer · chorus-aidlcFinal ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read the integrated code, check cross-task integration / architecture / security / regression / coverage, run tests. Invoke after the last task of an idea-rooted proposal (or the last Quick Task linked to the Idea) is verified; ends with a VERDICT comment on the Idea.