quick-dev-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. > **Tool namespace:** Chorus tools are exposed by the connected MCP server under a `mcp__chorus__` prefix on dsh (e.g. `mcp__chorus__chorus_create_tasks`). Bare names are used below for readability — prepend `mcp__chorus__` when invoking. See `chorus` for the full rule. --- ## 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, use `idea-chorus` + `proposal-chorus` instead. --- #...