planlisted

# Plan Ask: `$ARGUMENTS` Empty means the thing being discussed. If nothing is, ask what to plan. One question. ## First, read Read the code the change touches, its callers, and its tests before asking anything. Never ask what the codebase already answers. ## Then, ask Only the questions whose answers change the work. One at a time; wait for each answer. Stop the moment the smallest version is unambiguous. The usual ones: who calls this and what do they expect; what happens on failure; does it have to stay backward compatible; what is the deadline made of; what is explicitly out of scope. Three questions is normal. Ten means the ask isn't ready; say so. If a question can be answered faster by a two-line throwaway prototype than by asking, write it, run it, throw it away, and report what it showed. ## Then, write Half a page. These headings, this order: ``` # Plan: <one line> Goal. One sentence. The outcome, not the activity. Not doing. Explicit. The things that will be asked about later. Smallest version. Which rung of the ladder stopped it, and what that looks like. Steps. Numbered. Each small enough to finish and verify alone, each with its check: the test, the command, the thing to look at. What breaks at 3am. The items from the list that apply, and how each is handled. Rollback. How this is undone in five minutes. If it can't be, say so and why that's acceptable. Done means. The commands that will be run and what they must print. ``` Save it to `docs/plans/YYYY