SKILL.md
Structured Planning
Build a plan that another session can execute and verify without rediscovering the decision. Specify outcomes and dependencies tightly enough to prevent drift while leaving implementation choices to the code and evidence encountered during execution.
The user's instructions take precedence over this skill's guidelines. Planning does not add an approval requirement. If execution is already authorized, continue after the plan is ready; if the user requested only a plan, deliver the plan without starting implementation.
Size the Plan by Uncertainty
| Work shape | Planning depth |
|---|---|
| Clear, reversible change with a direct check | Execute with a brief mental or inline plan |
| Several dependent behaviors with known patterns | Record tasks, interfaces, and acceptance checks |
| Uncertain architecture or migration | Resolve decisive unknowns and plan a representative vertical slice |
| Work spanning agents, sessions, or environments | Preserve ownership, state, dependencies, and resumption instructions |
File count is a poor proxy for risk. A one-line authorization change can need more analysis than a mechanical rename across many files. Plan enough to expose the uncertain or irreversible parts, not enough to predict every edit.