df:quick

Execute ad-hoc tasks with atomic commits and STATE.md updates.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: df:quick
Source: https://github.com/AO-Cyber-Systems/devflow-claude/tree/main/skills/df-quick
Command: npx skills add https://github.com/AO-Cyber-Systems/devflow-claude --skill df-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a quick task with DevFlow guarantees (atomic commits, state tracking) but skip optional agents. Use when you want to do something small, quick, or ad-hoc without full objective ceremony.

Core Features & Use Cases

  • Spawns df-planner (quick mode) + df-executor(s) to run small tasks with DevFlow discipline.
  • Quick tasks live in .planning/quick/ and update STATE.md "Quick Tasks Completed" table to reflect progress.
  • Default: Skips research, job-checker, verifier. Use when you know exactly what to do and want rapid execution.

Quick Start

Ask the AI to perform a small, ad-hoc task using the quick workflow.

Frequently Asked Questions about df:quick

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

FAQPage Schema
How do I execute small ad-hoc tasks with atomic commits and state tracking?

Executing small ad-hoc tasks with atomic commits and state tracking requires a quick workflow mode that skips optional agents like research and verification, maintaining progress in a dedicated state file.

What is the best way to automate rapid one-off tasks across local projects?

The best way to automate rapid one-off tasks across local projects is using a quick task execution workflow that provides DevFlow guarantees like atomic commits without the overhead of full objective planning.

Do I need full objective ceremony for small local project task execution?

Full objective ceremony is not needed for small local project task execution. You can skip optional research and verification agents by using a quick mode designed for rapid, ad-hoc task completion.

How does state management work for quick tasks in a local project?

State management for quick tasks operates by tracking progress in a STATE.md file. Quick tasks live in a specific planning directory and update the completed tasks table to maintain state across executions.

When should I avoid using a quick task execution workflow?

Avoid using a quick task execution workflow when your project requires research, job-checking, or verification agents. It is built for situations where you know exactly what to do and want rapid execution.