Planning does not implement, branch, or commit. A single already-clear change uses /w-build. A blocking product gap uses /w-clarify. Stress-test a plan with /w-grill. Fog bigger than one session uses /w-wayfinder.
- Explore: if this turn has no reconciled exploration for the area, follow council steps 1–3, then continue.
- Goals: 3–7 bullets for scope, success, constraints, non-goals.
- Context: matching glob rule and skill, then topic MDX (or this repo’s docs path). Rules override skills. Inspect affected packages, README, scripts. Durable architecture: matching MDX/ADR. Generated outputs name an owning source; commands come from inspected scripts.
- Assumptions: 3–5 bullets. Defer product scope, secrets, and destructive ops.
- Tasks: ordered work with likely files and dependencies. Uncertain work first. Diagram only if relationships need one.
- Output: user’s path, else the repo’s existing plan file, else chat. Follow plan output.