auto-devflow

# Start Devflow Run a controlled **devflow**: the main agent stays the controller, each subagent owns one phase, and phase outputs are written to temporary handoff files before the next phase starts. Use this when the user says things like "开始解决这个 issue", "start this issue", "fix this bug end-to-end", "实现这个功能", or asks for a multi-agent workflow rather than a single-agent edit. ## Non-Negotiables - The main agent owns scope, approvals, TodoWrite, git safety, and final reporting. - Subagents do focused work only. Do not let a subagent silently broaden scope. - Use handoff files as the shared memory. Do not rely on hidden subagent context. - Run writable phases sequentially. Never run two coding subagents against the same checkout at the same time. - Ask the user before destructive operations, branch changes, commits, or scope expansion. ## Operating Modes Pick a mode during Intake and record it in `00-context.md`. ### Relaxed Mode Default for simple, low-risk tasks. Use relaxed mode when: - the request is small and localized - the likely change touches a few files with obvious ownership - failure impact is low and rollback is straightforward - the agent has not already made repeated mistakes on this task Relaxed flow: ```text Intake → Explore → Plan → Code → Review → Verify → Report ``` Plan review is optional. The main agent may self-check `02-plan.md` instead of dispatching a separate reviewer. ### Cautious Mode Use cautious mode when the user says the task is ...