saoplisted

# SAOP: the plan-first executor The most expensive mistake in AI-assisted work is building on a half-baked structure. A wrong assumption made at the start costs a whole block of work to unwind. SAOP removes that risk: it thinks a problem fully through, read-only, before the first line is written, and hands back a plan whose every endpoint is already checkable. "Executor" means this skill executes the SAOP *method*, the planning pass, end to end. It does not write the implementation; that begins only after you approve the plan. The method README is the "why"; this is the "how": https://github.com/kaposty/saop ## Read-only during the pass, and Plan Mode The pass plans; it does not implement. It reads and researches (Read, Grep, Glob, WebSearch, WebFetch, and Bash for read-only checks like `git log`) and hands the plan back as text. Implementation of a planned task begins only after you approve, in a fresh message; the one exception is the triviality gate's light path below, which states its single change first and applies it only if you do not object. Treat destructive shell commands as out of scope during the pass. "Read-only" is only as strong as what enforces it. The frontmatter drops the editing tools (Edit, Write, NotebookEdit) while the skill is active, but that restriction lifts on your next message, so it is a safety net, not a lock. The real guarantee is **Plan Mode**: there the harness blocks every state-changing command until you approve, across turns. So the f