planninglisted

# Planning Turn a request into a plan another mind can execute without interpretation. The enemy is the plan that restates intent and exports discovery to the executor. The overcorrection is a full edit specification for two edits the current session can order in two lines. ## Activation gate Draw `A → B` when B cannot build, test, or preserve data before A lands. Zero or one edge for this session belongs in `implementing-batch`. When this session executes, nobody asked for a plan, and an upstream `shaping` brief lists every edge and places A before B for each one, use that order without running this skill. ## Intake - Restate the actual goal in one sentence; plan against that restatement, not the prompt's phrasing. - Resolve a vague referent from the first non-empty source: working-tree diff, most recent failing check, then last touched file. - Separate hard requirements from incidental wording; record what the plan will not do as explicit non-goals. - Decide every choice the user would not notice and record it in the plan; do not interview. - Read an issue reference, `#<n>` or an issue URL, with `gh issue view <n> --json number,title,body,url`: a body whose first line is `<!-- exo:spec -->` is a shaped brief, planned as a spec file would be and never shaped again, and the plan's `## Goal` names `#<n>` so the finished pull request closes it. - Ask, before writing, only what blocks planning: the first non-empty source holds two or more candidate referents and the request