auto-executelisted

# auto-execute Implementation controller. Executes approved plan slices without reopening product scope. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble auto-execute owns execute-stage orchestration, route selection, state, and scope. Direct implementation and subagent implementation are two routes inside this skill. It does not reopen product scope or modify the approved plan's intent. Execute and verify one approved slice at a time inside the selected execution window. Continuation is the default after a verified slice; checkpoints and STOP conditions are the exceptions. An execution window is a context-management batch, not a completion boundary. Loading discipline: keep the active slice, execution-window metadata, acceptance criteria, route metadata, verification commands, and active files in context. Load linked detail files and traceability IDs for the active slice only; read wider project files only when implementation correctness requires it. Read `.agent/.automaton/references/CONTEXT-BUDGET.md` when wider reads threaten context pressure. ## Quality Gate Before marking a slice complete: - Keep edits inside the active slice. - Investigate root cause before fixing bugs; read `references/debug-protocol.md` only when bounded diagnosis needs more structure. - Record verification evidence before advancing or selecting the next slice. - Read `references/quality.md` when the diff looks clever, defensive, or broader