Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
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
Stakeholder elaboration is needed to clarify requirements
The work impacts architecture or shared components significantly
For complex work, use /idea + /proposal 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".
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 acceptanceCriteriaItemsreplaces 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>"]
})
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. Spawn the required independent task-reviewer sub-agent as described in /develop, wait for it, and read the newest VERDICT: Task comment. 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:
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.
Session Integration
Quick Tasks work with Claude Code Agent Teams just like proposal-based tasks:
Team Lead: create quick tasks, then assign to sub-agents via task UUIDs
Sub-agents: the Chorus Plugin auto-injects session context — just pass sessionUuid to chorus_update_task and chorus_report_work
Session lifecycle is fully automated by the plugin
Tips
Keep Quick Tasks small — if you need more than 2-3 tasks, consider using /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 show up 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
Next
For full task lifecycle details, see /develop
For admin verification, see /review
For the standard planning flow, see /idea and /proposal
