Skip to content
tishad.net
SearchCtrl K

Lessons / Part 10. Coding agents, commands and skills

66 Approving a plan is not telling it to start

A go that covers one named step, and a hook rather than a written rule in front of the step that cannot be undone.

What people usually ask

Looks good, go ahead.

What comes back

The whole plan runs to the end, including step 4, which renamed two thousand raw files in place and cannot be reversed.

Ask this instead

Go means step 1 only: write inventory.csv as plan.md describes it, then stop. Before you start, give me one line on how you read this message. Do not begin step 2 until I type "step 2".
Step 4 (rename the raw files in place) must never run on a go alone. Put it behind a hook that runs before every shell command and refuses any command that writes under raw/, so that a sentence in a file is not what stands between the plan and my data. Show me the hook, then show me the refusal once on a dry run.

Attach: Nothing.

Why it works: The go is narrowed to one named file, and the step that cannot be undone is stopped by something that runs rather than by a rule the agent may not read.

Drafted with Fable 5.1 from my notes; chosen and edited by me.