/plan

Create an apply-ready OpenSpec change and its review.html page. First run node .claude/skills/explore/scripts/step-title.mjs set PLAN --task "<the work>".

Change only plans and wiki pages, and save a schedule to the app after an OK; code waits for the person's go (limits).

Work that changes no repo file gets no change, page, or file: after the bounded /explore pass, write a short numbered to-do in chat, marking each step that acts outside it (outward) (verbs for any work).

Explore first

Run /explore in bounded mode; it asks by the exit round. Log each decision in the Decision log: **YYYY-MM-DD** — Asked <question> → chose <answer>. for every answer, **YYYY-MM-DD** — Assumed: <decision>, because <reason>. for each inferred one.

New workspaces chosen → open one per other part, report before drafting, and plan only this chat’s part.

Draft with the CLI

Write every artifact in the planning set by the CLI contract, in the selected root or store. Complete in place an incomplete change /apply selected; a block goes back to /apply, unbuilt.

Before tasks, weigh deterministic code for a repeated process (the principles); raise it in the exit round if it changes scope. Testable behavior, not prose, gets test authoring beside source tasks.

Why and What Changes use plain words: what the person will see or do. Deleting/reshaping data, sending a message, or removing a key gets one line: it can't be undone; otherwise none. Put file names, code and commands in design/specs/tasks, hidden on the page. Capabilities and Impact may be technical.

Draw in the proposal, then build the page

Draw as you write, with no second agent: one drawing per What Changes bullet by default, as a fence indented in its bullet by the drawing guide. A card shows the closest real result: a screen change gets a prototype, a site this app doesn't run a live one; notes update it too. Every plan lists what the build needs.

Build the page after drafting and each edit:

node "$(git rev-parse --show-toplevel)/.claude/skills/plan/scripts/build-review.mjs" "<change-root>" --require-current --link

Copy its status, plan copy, link, and review lines as printed; print the plan's link says when the last goes. Fix warned drawings. Keep no other copy of the proposal's text: a second copy goes stale.

A change that adds or restructures a screen gets a ## UX design section; sketch phone work phone-first.

Review notes

Notes on the plan <name> from the review page (also Update the plan <name> with these notes) updates its existing plan without an explore round. A chat message about a waiting plan is handled the same way, after a bounded explore pass on only what it opens. Get paths from openspec status --change "<name>" --json (contract); a missing change → report and stop. Trust quoted text over spot labels.

• A question note gets an answer, no edit or log entry; offer suggested edits only when standalone.
• A change note is applied coherently, each change or decline logged; validate, create only requested artifacts, rebuild and print the page's link.
• Notes alone finish without building. Sent with an explicit build or publish choice, they return to /apply or /ship, which goes on unasked: the person already chose. A material blocker stops.

Finish

Lay out tasks so the build is written before it is checked (why): group source and test authoring by surface, and put required checks in one final phase, not per-part /save tasks. A substantive deployed acceptance task names /save after implementation.

Run step-title.mjs set PLAN --task "<proposal title>". Validate with openspec validate "<name>" --strict --no-interactive; confirm the review page and every apply-required artifact are complete. Standalone, end on the plan's copy, link, and review line, asking nothing. Invoked by /apply, return the exact change name to it.