Agent skill

Quick Dev Chorus

Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.

AGPL-3.0Auto-check passedProduct & Project Management

Install Quick Dev Chorus

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/public/skill/quick-dev-chorus .claude/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .claude/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/public/skill/quick-dev-chorus .agents/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .agents/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/public/skill/quick-dev-chorus .cursor/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .cursor/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Chorus-AIDLC/Chorus.git --path public/skill/quick-dev-chorus

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/public/skill/quick-dev-chorus .gemini/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .gemini/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .github/skills && cp -r skills-src/public/skill/quick-dev-chorus .github/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .github/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Chorus-AIDLC/Chorus quick-dev-chorus --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/public/skill/quick-dev-chorus .opencode/skills/quick-dev-chorus && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "quick-dev-chorus" agent skill from https://github.com/Chorus-AIDLC/Chorus/tree/main/public/skill/quick-dev-chorus into .opencode/skills/quick-dev-chorus/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-dev-chorus", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: quick-dev-chorus
GitHub stars: 1.2k
Token cost: ~2k tokens
SKILL.md length: 761 words
Files: 2
Skills in repo: 64
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.

Works in 8 steps: Create a Quick Task → Claim the Task → Edit Details (if needed) → …
Product & Project Management work in your project
SKILL.md covers Overview, Pre-Flight: Permission Check, Tools and Workflow, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Quick Dev Chorus is an agent skill from Chorus-AIDLC/Chorus. Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `package.json`).

It sits in Product & Project Management. The repository describes itself as: The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle). The licence is AGPL-3.0.

When your agent uses it

Product & Project Management work in your project

Example prompts

“/quick-dev-chorus”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Create a Quick Task
Claim the Task
Edit Details (if needed)
Start Working
Report Progress
Self-Check Acceptance Criteria
Submit and Run Independent Review
Permission-Aware Verification

What it can do on your machine

Read from SKILL.md and the folder at commit 4754822. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quick Dev Chorus loads about 2k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 761 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~26
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Chorus-AIDLC/Chorus at commit 4754822, republished under its AGPL-3.0 licence (© Chorus-AIDLC). 761 words, ~1,979 tokens.

Download SKILL.mdSave it as .claude/skills/quick-dev-chorus/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: quick-dev-chorus
description: Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.
license: AGPL-3.0
metadata.author: chorus
metadata.version: 0.17.0
metadata.category: project-management
metadata.mcp_server: chorus

Quick Dev Skill

Skip the full AI-DLC pipeline (Idea → Elaboration → Proposal → Approval) and create tasks directly. Ideal for small, well-understood work. The goal is for agents to autonomously record their development work and verify task completion through structured acceptance criteria.

Overview

The standard AI-DLC flow ensures quality through structured planning, but adds overhead that slows down small tasks. Quick Dev provides a lightweight alternative:

check explicit task:admin permission → create/claim → implement → self-check AC → submit → independent task review → verify or hand off

Use Quick Dev when:

Bug fixes with clear reproduction steps
Small features (< 2 story points)
Post-delivery patches and gap-filling after a proposal's tasks are done
Prototype or exploratory tasks
Urgent hotfixes that can't wait for proposal review

Do NOT use Quick Dev when:

The feature needs a PRD or tech design document
Multiple interdependent tasks require upfront planning
Stakeholder elaboration is needed to clarify requirements
The work impacts architecture or shared components significantly

For complex work, consider using the idea and proposal skills instead.

Pre-Flight: Permission Check

Call chorus_checkin and inspect the active agent's effective permissions. Set canVerifyTask to true only when chorus_checkin().agent.permissions.task explicitly contains "admin" (the task:admin permission).

Never infer verification authority from the agent's name, persona, preset/role label, task ownership, or tool availability. Do not ask whether to self-verify: the explicit permission determines the terminal path.

Tools

Tool	Purpose
`chorus_create_tasks`	Create task(s) — omit `proposalUuid` for standalone Quick Task, or pass it to attach to an existing proposal
`chorus_update_task`	Edit task fields (title, description, priority, AC, dependencies) or change status
`chorus_claim_task`	Claim a task (open → assigned)
`chorus_report_work`	Report progress with optional status update
`chorus_report_criteria_self_check`	Self-check acceptance criteria before submitting
`chorus_submit_for_verify`	Submit for admin verification
`chorus_admin_verify_task`	(admin only) Verify task — use when self-verification is approved

Workflow

Step 1: Create a Quick Task

acceptanceCriteriaItems is required — chorus_create_tasks rejects any task without at least one non-blank criterion (and rejects the whole batch if any task is missing them). These are also the foundation for self-checking in Step 6. Write specific, testable criteria that you can objectively verify after development. Vague AC like "works correctly" defeats the purpose; prefer "returns 200 on GET /api/foo with valid token".

chorus_create_tasks({
  projectUuid: "<project-uuid>",
  tasks: [{
    title: "Fix login redirect loop on Safari",
    description: "Safari loses session cookie after redirect...",
    priority: "high",
    storyPoints: 1,
    acceptanceCriteriaItems: [
      { description: "Login works on Safari 17+", required: true },
      { description: "Existing Chrome/Firefox behavior unchanged", required: true }
    ]
  }]
})

proposalUuid is optional:

Omit for standalone quick tasks (bug fixes, hotfixes, exploratory work)
Pass to attach the task to an existing proposal — useful for gap-filling, follow-up patches, or continuing work after a proposal's initial tasks are delivered

Step 2: Claim the Task

chorus_claim_task({ taskUuid: "<task-uuid>" })

Step 3: Edit Details (if needed)

Use chorus_update_task to refine the task after creation. Tasks always have AC (creation requires them), but update them when your understanding changes during development. Passing acceptanceCriteriaItems replaces the task's criteria with the provided non-empty set; omit the field to leave them unchanged (it cannot be used to clear AC).

chorus_update_task({
  taskUuid: "<task-uuid>",
  description: "Updated with more details...",
  acceptanceCriteriaItems: [
    { description: "Login works on Safari 17+", required: true },
    { description: "Added CSRF token handling", required: true }
  ],
  addDependsOn: ["<other-task-uuid>"]
})

Step 4: Start Working

chorus_update_task({ taskUuid: "<task-uuid>", status: "in_progress" })

Step 5: Report Progress

chorus_report_work({
  taskUuid: "<task-uuid>",
  report: "Fixed Safari cookie issue:\n- Root cause: SameSite=Strict incompatible with redirect\n- Changed to SameSite=Lax\n- Commit: abc1234"
})

Step 6: Self-Check Acceptance Criteria

chorus_report_criteria_self_check({
  taskUuid: "<task-uuid>",
  criteria: [
    { uuid: "<ac-uuid-1>", devStatus: "passed", devEvidence: "Tested on Safari 17.2" },
    { uuid: "<ac-uuid-2>", devStatus: "passed", devEvidence: "Chrome/Firefox regression tests pass" }
  ]
})

Show full SKILL.md (313 more words)Show less

Step 7: Submit and Run Independent Review

chorus_submit_for_verify({
  taskUuid: "<task-uuid>",
  summary: "Fixed Safari login redirect loop. Changed SameSite cookie policy. All AC passed."
})

Submitting is not final verification. Invoke the required independent task reviewer with the host agent's sub-agent mechanism, wait for it, and read THIS round's VERDICT: Task comment — the one posted after your dispatch, not an older round's. PASS and PASS WITH NOTES continue. On FAIL, do not verify or hand off: fix every unresolved BLOCKER, repeat AC self-check and submission, then run a fresh independent task review.

Step 8: Permission-Aware Verification

With explicit task:admin, after every required AC self-check passes and independent review has no unresolved BLOCKER, verify and continue autonomously:

chorus_admin_verify_task({ taskUuid: "<task-uuid>" })

Without explicit task:admin, do not call the admin tool. Post an evidence-rich comment on the Task containing AC results, test evidence, the latest independent-review verdict, and the exact requested action. @mention the responsible human (prefer chorus_checkin().agent.owner) to perform admin verification, then end the current turn.

This handoff applies in interactive and headless daemon sessions. Do not use an interactive prompt, poll for the human response, or rely only on generic notifications.

Tips

Keep Quick Tasks small — if you need more than 2-3 tasks, consider using a proposal
Acceptance criteria are required at creation time — chorus_create_tasks rejects tasks without them. They are your self-check contract; specific, testable AC enables autonomous verification and makes the entire workflow self-contained
Use chorus_update_task to refine tasks (including AC) after creation rather than deleting and recreating
Pass proposalUuid to attach follow-up or gap-filling tasks to an existing proposal — this keeps related work grouped in the same project context and DAG
Quick Tasks appear in the same project task list and DAG as proposal-based tasks
Agents with explicit task:admin continue autonomously after AC and independent review pass; all others use the evidence-rich asynchronous human handoff

For full task lifecycle details, download <BASE_URL>/skill/develop-chorus/SKILL.md
For admin verification, download <BASE_URL>/skill/review-chorus/SKILL.md
For the standard planning flow, download <BASE_URL>/skill/idea-chorus/SKILL.md and <BASE_URL>/skill/proposal-chorus/SKILL.md
For platform overview, download <BASE_URL>/skill/chorus/SKILL.md

Files

SKILL.md and 1 other file in public/skill/quick-dev-chorus of Chorus-AIDLC/Chorus.

SKILL.md
package.json

Open the folder on GitHubat commit 4754822

Compare with similar skills

Quick Dev Chorus next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quick Dev Chorus compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Quick Dev Chorus this skillChorus-AIDLC/Chorus	1.2k	—	~2k	Automated safety check: Pass	AGPL-3.0	today
CCPM Project Managementautomazeio/ccpm	8.4k	—	~1.1k	Automated safety check: Pass	MIT	6 mo ago
Trellis Brainstormanjiemo/SunnyBeach	178	7 repos	~4k	Automated safety check: Pass	Apache-2.0	26 days ago
Ouroboros PM InterviewQ00/ouroboros	6.2k	1 repos	~5.7k	Automated safety check: Pass	MIT	today
Jira Natural Language Interfacejjmartres/opencode	133	3 repos	~1.7k	Automated safety check: Pass	MIT	5 mo ago
Project Planneradrianpuiu/claude-skills-marketplace	100	1 repos	~6k	Automated safety check: Pass	None	4 mo ago

Similar skills

CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Trellis Brainstorm
anjiemo/SunnyBeach
Guides collaborative requirements discovery before implementation.
178 GitHub starsUsed in 7 repos~4k tokens
Product & Project ManagementAuto-check passed
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
6.2k GitHub starsUsed in 1 repo~5.7k tokens
Product & Project ManagementAuto-check passed
Jira Natural Language Interface
jjmartres/opencode
Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.
133 GitHub starsUsed in 3 repos~1.7k tokens
Product & Project ManagementAuto-check passed
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
100 GitHub starsUsed in 1 repo~6k tokens
Product & Project ManagementAuto-check passed
Review
fossasia/eventyay-interpretation
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match…
1.6k GitHub starsUsed in 35 repos~996 tokens
Product & Project ManagementAuto-check passed

Questions about Quick Dev Chorus

What does Quick Dev Chorus do?

Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify. Quick Dev Chorus is an agent skill from Chorus-AIDLC/Chorus. Quick Task workflow — skip Idea→Proposal, create tasks directly, execute, and verify.

When should I use Quick Dev Chorus?

Quick Dev Chorus fits situations like: product & Project Management work in your project.

How do I install Quick Dev Chorus in Claude Code?

Run `npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a claude-code`. Or copy the skill folder (public/skill/quick-dev-chorus in Chorus-AIDLC/Chorus) into .claude/skills/quick-dev-chorus in your project. Claude Code loads it when a task matches its description.

How do I install Quick Dev Chorus in Codex?

Run `npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a codex`. Or copy the skill folder (public/skill/quick-dev-chorus in Chorus-AIDLC/Chorus) into .agents/skills/quick-dev-chorus in your project. Codex loads it when a task matches its description.

Can I use Quick Dev Chorus in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Chorus-AIDLC/Chorus --skill quick-dev-chorus -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quick-dev-chorus, .gemini/skills/quick-dev-chorus, .github/skills/quick-dev-chorus and .opencode/skills/quick-dev-chorus in your project.

What does Quick Dev Chorus need to run?

SKILL.md names no scripts, command-line tools or credentials: Quick Dev Chorus is instructions for the agent only.

Does Quick Dev Chorus access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quick Dev Chorus safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quick Dev Chorus use?

Quick Dev Chorus is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quick Dev Chorus use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quick Dev Chorus?

Skills that share tags, products or a category with Quick Dev Chorus: CCPM Project Management (automazeio/ccpm, 8.4k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars) and Jira Natural Language Interface (jjmartres/opencode, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quick Dev Chorus?

Chorus-AIDLC (a GitHub organization) maintains it in Chorus-AIDLC/Chorus, which has 1,192 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 7, 2026.

Source: Chorus-AIDLC/Chorus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Quick Dev Chorus

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Quick Dev Skill

Overview

Pre-Flight: Permission Check

Tools

Workflow

Step 1: Create a Quick Task

Step 2: Claim the Task

Step 3: Edit Details (if needed)

Step 4: Start Working

Step 5: Report Progress

Step 6: Self-Check Acceptance Criteria

Step 7: Submit and Run Independent Review

Step 8: Permission-Aware Verification

Tips

Next

Files

Compare with similar skills

Similar skills

More from Chorus-AIDLC/Chorus

Related

Questions about Quick Dev Chorus