drafting-planslisted

# A plan is an execution contract The plan exists so the user can see what you are about to spend their time and money on, and so you cannot quietly drift once you start. It is not documentation. It is the thing you are held to. Answer the user in whatever language they wrote in. ## Preconditions An approved brief, and a capability resolution. Planning without the brief means planning something nobody agreed to. Planning without the resolution means writing steps that may have no way to run. ## Step schema Every step carries these six planning fields. Execution adds and maintains a seventh, `status`, which starts at `pending` — see [the template](templates/plan.md). A step missing `verify` cannot be checked; a step missing `provider` may be unrunnable. ```markdown ### Step 3 — Collect published pricing for the shortlist - capability : web-research - provider : <installed research skill> - fallback : fetch tool over user-supplied URLs - verify : pricing captured for all 4 vendors in .superclarity/<task>/data/pricing.md - depends : Step 2 - risk : low ``` ## What makes a step good | Requirement | Meaning | | --- | --- | | **Independently verifiable** | It ends in a named artifact or an observable state. "Research the market" cannot be verified; "8 competitor pricing pages saved under `data/`" can. | | **Sized to one capability** | Roughly one or two operations. A step spanning three capabilities is three steps. | | **Explicit dependencies** | If step 4