plan git:20260812.eb0ffc1A

Immutable. This exact content never changes and is served at /api/v1/blob/dd5640e6be0427ce.

---
name: plan
description: Build a verification-first implementation plan for new features, major refactors, ambiguous work, or any multi-step change whose acceptance criteria are not yet falsifiable. Use when the user asks for a plan or before risky work; request approval only when ambiguity, high stakes, destructive action, a public-contract choice, or a scope change requires it.
---

# Plan — make the change falsifiable

Use the lightest plan that removes uncertainty. Planning is a design protocol, not a mandatory pause before every edit.

## 1. Bound the work

State the goal, non-goals, affected modules, public interfaces, and configuration keys. Mark assumptions separately from known facts. Inspect the repository before treating a guessed interface or command as real.

## 2. Define proof

For every requirement, name an observable pass/fail condition and the command or inspection that can test it. Do not invent an exact output line before the check exists; define the decisive signal precisely enough that success and failure cannot both satisfy it.

If coverage is missing, plan the smallest red-before-green test or fixture first. Include the full verification tier for closeout.

## 3. Choose reversible steps

Break the work into independently checkable edits. Name compatibility risks, data or contract migrations, rollback points, and any state that cannot be recovered automatically.

## 4. Decide whether to pause

Ask for approval before editing only when the remaining choice is ambiguous and materially changes the result, or when the next action is high-stakes, destructive, changes a public contract, expands scope, deploys, spends money, or affects production. Ask one decision-shaped question.

Otherwise, show the concise plan and proceed. Update it when evidence invalidates a step; do not preserve a stale plan for ceremony.