plugins/devflow/skills/quick/SKILL.md
Small features (single executor, no planner, no verifier) — between micro (1-line) and build (multi-subsystem). Cutoff: <5 files, <200 LOC, no new abstractions. Use when the change is too big for /devflow:micro but doesn't warrant full /devflow:build planning. Triggers on: "small change", "small feature", "5-file change", "isolated bug fix", "do this small task", "tackle this small change", "make a quick pass"
npx skillsauth add ao-cyber-systems/devflow-claude quickInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Cutoff (advisory, enforced by convention):
Smaller? Use /devflow:micro — sub-30-LOC, single-file, ~2k token cost.
Larger or multi-subsystem? Use /devflow:build — full plan/execute/verify pipeline.
Quick mode is the same system with a shorter path:
.planning/quick/ separate from planned objectivesDefault: Skips research, job-checker, verifier. Use when you know exactly what to do.
--full flag: Enables job-checking (max 2 iterations) and post-execution verification. Use when you want quality guarantees without full milestone ceremony.
Intent defaults for quick mode: work: bugfix (smallest TDD posture commensurate with quick's purpose). CLAUDE.md absorption is skipped — quick mode honors the no-ceremony promise rather than applying user playbook directives that would require strict TDD on a typo fix. To opt back into the user playbook, prefer /devflow:build or /devflow:plan-objective --work <type> instead.
</objective>
<execution_context> @~/.claude/devflow/workflows/quick.md </execution_context>
<context> @.planning/STATE.md $ARGUMENTS </context> <process> Execute the quick workflow from @~/.claude/devflow/workflows/quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits). </process>development
Resolve a parked decision and resume autonomous execution. Use when you see a pending DECISION-NNN.md in .planning/decisions/pending/, when the user wants to choose an option for a blocked checkpoint:decision, or when you need to tell the executor which option to take. Triggers on: "resolve decision", "decide DECISION-", "pick option for DECISION-", "unblock DECISION-", "answer DECISION-", "choose option for decision", "I want option-a", "go with option-b", "my answer is".
development
Orchestrate a multi-step DevFlow workflow by chaining skills. Use when the user wants to invoke a sequence of skills as one ask (e.g., "build and sync to github", "research, plan, then build", "ship and announce"). Triggers on: "ship X to Y", "build and X", "plan and X", "X then Y", "in one go", "as a chain", "all in sequence", "chain", "ship-and-sync", "research-plan-build"
testing
Stamp a new polyglot monorepo using the AO Cyber Systems scaffold — root CLAUDE.md with Layout table, per-area CLAUDE.md, path-filtered CI workflows, comprehensive .gitignore, and the no-binaries pre-commit hook config. Use this for new product monorepos (the 5-monorepo architecture: aodex, aosentry, eden-biz, politihub, aohealth, plus future ones). Triggers on: "new monorepo", "scaffold a monorepo", "set up a monorepo", "create a new product monorepo".
development
Validate that a monorepo follows the AO Cyber Systems layout convention — root CLAUDE.md declares every area, every area has its own CLAUDE.md, no compiled binaries are tracked in git. Reads the root `CLAUDE.md` Layout table, walks the working tree, and reports drift in a single Markdown summary. Standalone — works on any repo. Triggers on: "audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".