sddl-executor

Use a stage-scoped executor that reads the Stage Plan table in plan.md and runs exactly one stage per invocation. Each stage requires explicit user approval before starting, and the run stops automatically after completion rather than continuing to the next stage.

Maintain an execution-log.md ledger that appends an entry per attempted or completed stage, recording approvals, changed files, quick checks, and blockers. Pair it with a state.yaml file tracking current stage, lifecycle status, and next action so work can resume safely.

The stage stops before widening scope when drift is detected, such as work requiring deliverables not in plan.md. The drift is recorded in execution-log.md and routed back to the user for approval, replanning, or clarification.

No. The executor performs no git side effects: no commits, stashes, rebases, or even git add. Staging files belongs to the orchestrator and only on explicit user request.

QA review is recommended when a completed stage touched code with non-trivial blast radius, reached a meaningful checkpoint, or surfaced warnings in quick checks. The executor records the recommendation in execution-log.md and state.yaml but never auto-runs the review.