quick-dev

Automates lightweight task cycles from creation to verification for small fixes and patches.

1.1k|99|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill quick-dev-chorus-aidlc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-dev
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/public/chorus-plugin/skills/quick-dev
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill quick-dev-chorus-aidlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quick Dev addresses the overhead of the full AI-DLC workflow for small tasks by enabling a lightweight, autonomous flow.

Core Features & Use Cases

  • Create quick tasks directly with explicit acceptance criteria.
  • Claim, progress update, and self-check criteria to enable autonomous verification.
  • End-to-end lifecycle from creation to verification, with optional admin verification.

Quick Start

Create a standalone quick task for a small bug fix with explicit acceptance criteria and minimal planning.

Frequently Asked Questions about quick-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate small bug fixes with acceptance criteria and self-checks?▼

You can automate small bug fixes by creating quick tasks with embedded acceptance criteria, progressing through autonomous cycles, and running self-checks before submitting for optional admin verification.

What is the best way to manage fast turnaround patches without full planning overhead?▼

Managing fast turnaround patches is best handled by bypassing full planning workflows and enabling an autonomous quick-task cycle from task creation directly through to verification.

Can I embed acceptance criteria directly into a quick task for autonomous verification?▼

Yes, you can embed acceptance criteria directly into a quick task, allowing the system to perform self-checks against those criteria to enable autonomous verification.

Does the quick task workflow support end-to-end lifecycle management for small patches?▼

The quick task workflow supports end-to-end lifecycle management for small patches by handling task creation, progress updates, criteria self-checks, and final submission for verification.

When should I avoid using a lightweight autonomous task flow?▼

You should avoid using a lightweight autonomous task flow for complex deliverables that require comprehensive planning, as it is specifically designed to bypass full planning for small bug fixes.

Why does my quick task require a self-check before submission?▼

Your quick task requires a self-check before submission to validate the work against the embedded acceptance criteria, ensuring the patch meets requirements before optional admin verification.