Plan ceremony

Plan ceremony stance: light

A plan is a short message in chat: what will be built, the steps with one exit test each, and the decisions the user must make, numbered. No plan file is required, no card validator runs.

Wait for an explicit go-ahead before implementing, then implement the whole plan without per-step confirmation. If the user asks for a written plan, the plan-authoring skill still knows the full shape.

Plan ceremony stance: Review Card and build gate

Invoke the plan-authoring skill before writing or revising a plan file. Non-negotiable even if it is skipped: the file opens with a Review Card — title, two-sentence verdict, at-a-glance bullets, one diagram, numbered steps with exit tests, numbered decisions, risks — capped at 70 lines, no ## Context, the rest below a --- under # Addendum. Plan inside plan mode where it exists: it names the file, its pane is the review surface, its approval is the gate. Post it — verdict, bullets, decisions verbatim, a link — then ExitPlanMode, rename to a topic slug, hand over the path. Refresh Changed this round. Elsewhere: Reply build to proceed.