auto-devflow

# Adaptive Devflow Run the **lowest sufficient devflow**. The main agent remains the controller, but the amount of ceremony and delegation scales with task complexity: ```text lite < normal < pro < max < ultra ``` A lower mode may absorb a phase into the controller; it must not discard that phase's responsibility. For example, `lite` replaces a review subagent with a controller self-review, not with no review. ## Non-Negotiables These rules apply in every mode: - The main agent owns scope, mode selection, approvals, TodoWrite, git safety, and final reporting. - Use the smallest safe mode, but never trade away correctness, security, or required verification to save steps. - Subagents do focused work only. Do not let a subagent silently broaden scope. - Run writable phases sequentially. Never run two coding agents against the same checkout at the same time. - Ask before destructive operations, branch changes, commits, or scope expansion. Never commit unless the user explicitly requested it. - Inspect the actual diff and collect verification evidence before claiming completion. - Treat user-visible behavior, public contracts, persistent data, security boundaries, and irreversible operations as risk signals, regardless of file count. ## Select a Mode Accept an explicit mode in forms such as: ```text /auto-devflow lite fix the typo /auto-devflow pro implement issue 123 use max mode for this migration ``` Selection order: 1. If the user explicitly names a mode, use it as...