quicklisted

# Quick (`/flow:quick`) ## Overview Skip brainstorming, planning, and wave execution for tasks that are too small to justify them. **Core principle:** One agent, one pass, critic gate, done. **Agent selection:** `welder` by default; `guido` for design/naming questions; `scout` for research. Full routing matrix in Step 3 below. **Invocation:** ``` /flow:quick "add timeout param to retry" /flow:quick "fix import path in auth module" /flow:quick "rename voiceId to voice_id throughout" ``` The task description is passed inline. No spec file. No plan file. No waves. --- ## When to Use Quick Mode **Appropriate for:** - Bug fixes touching 1-2 files - Adding or renaming a parameter - Fixing a typo or incorrect import - Updating a comment or docstring - Adjusting a constant or default value - Any task where writing a spec would take longer than the fix itself **Not appropriate for:** - New features that touch 3 or more files - Architecture changes (new modules, new data models, interface changes) - Anything the user would want a spec or design discussion for first - Tasks with multiple independent sub-tasks - Anything requiring database migrations or security-critical logic **If the scope is unclear:** estimate it first (Step 1). If the estimate exceeds 2-3 files, stop and suggest `/flow:brainstorm` instead. --- ## Step 1: Estimate Scope Before dispatching an agent, estimate how many files this task will touch. Read the relevant files. Look at: - The file most likely to