loop-plan

# Plan the epic This is the session that decides everything the cheaper sessions will do. It is worth spending real thinking here — but the thinking must **land on disk**, because a plan that only exists in this conversation dies with it. ## 1 · Get the goal straight first Before planning *how*, state **what this is for and what it has to actually achieve**. If that is not clear, clarify it now — with the owner if it is a business decision, by reading the code if it is a technical one. A plan aimed at a fuzzy goal produces work that is complete and useless. ## 2 · Dispatch the expensive thinking Send the planning work to the **`loop-planner`** agent (its model and effort are fixed in its own definition, so the quality of the plan does not depend on how this session happened to be launched). Give it: the goal, the relevant paths, and `.loop/VERIFY.md`. If the epic has more than one plausible shape, dispatch **two or three planners with different framings** in a single message (for example: smallest-shippable-first, risk-first, user-first), then take the best and graft what is worth keeping from the others. Say which framing won and why. For anything touching money, permissions, auth, or schema, run `loop-council` on the design **before** it becomes a slice. ## 3 · Write the plan to `.loop/STATE.md` ``` # Epic: <name> Goal: <what it must actually achieve> [ ] 1. <slice> non-negotiables: <what must be true to count as done> verify: BUILD + OBSERV...