/apply

Build the chosen plan. Run node .claude/skills/explore/scripts/step-title.mjs set APPLY --task "<plan or to-do title>" before a build, to-do, or preview.

No repo file → work the to-do. Repo code or process, mini apps included → resolve the plan.

Resolve the plan first

Build the change this chat is about, found by the rungs. An argument naming no existing change is intent for a new plan. In /ship, an archive path is that change: skip status, add the failures as a task, and build.

Attached review notes → apply them to the existing change first, then keep building.

Check applyRequires in openspec status --change "<name>" --json:

• All done → apply-ready; continue.
• The selected change is incomplete → invoke the plan skill to complete it in place.
• No change, clear intent → invoke plan with that intent.
• Unclear intent → ask before any plan or code.

/apply authorizes planning and building. After /plan, verify the applyRequires closure; paused/blocked → report and stop. Otherwise keep its exact name and build in a helper.

At all-tasks-complete, even at invocation, finish with a preview, after a second look when this run built. Final acceptance's saved CI preview skips upload, then joins steps 4 and 5. Invoked by /ship, return after the second look, with no upload or /save.

Build in a helper

A .scratch/<name>-prototype copy → first run node .claude/skills/plan/scripts/prototype.mjs finish "<name>". Use a fresh helper on the parent's model, free of the planning talk: Agent (general-purpose) in Claude Code, a sub-agent in Codex. Prompt: the exact change name, then read $(git rev-parse --show-toplevel)/.claude/skills/apply/references/build-helper.md, then build. Add store <id> when selected, and inside /ship if so. The brief owns its work, its build order, and its return.

Let it build unwatched, with the longest host wait (the Agent call in Claude Code, wait_agent in Codex), waiting again on a timeout: don't narrate waits or read its files; message it only with an answer or a stop.

Act on reports:

• A question → ask the person in the shared ask format, log the answer as an Asked Decision-log line, then start a new helper. Inside /ship, a safe pick is logged Assumed, not asked.
• A blocker → report it and stop, ending with the ways to clear it.
• Final acceptance → once the build and its tests are written, run /save and the retained live acceptance. Tick only what you saw pass; a blocked or failed check stays unticked and stops.
• All done → confirm no unticked box, relay its local checks: line, then handle all-tasks-complete above.

No helper, or inside one → follow the brief inline.

A second look

Start a fresh helper as above, prompted with the change name, then read $(git rev-parse --show-toplevel)/.claude/skills/apply/references/review-helper.md, then review. Route its findings by fix it or ask: fix → a new build helper, which may dispute one with a reason, then the reviewer rereads; two rounds at most. The rest → one question, as above. No helper → say no review ran.

Finish with a preview

1. Did the app change? CI's own check, DEFAULT_BRANCH=main bash "$(git rev-parse --show-toplevel)/.github/scripts/app-untouched.sh" --worktree: untouched=true → skip the upload and say so in one line.
2. Upload the preview from this host, bash "$(git rev-parse --show-toplevel)/scripts/cf-preview.sh" --alias "<change-name>", with the Cloudflare credential from the primary worktree's .env (secrets). Can't run (no stack pack, no credential) → say why in one line.
3. Catch loosened checks: DEFAULT_BRANCH=main node "$(git rev-parse --show-toplevel)/.github/scripts/loosened-checks.mjs" --worktree. Fix each file marked needs a reason: switch the check back on, or add the Check: bullet when the plan settles it, else ask. Rerun until it exits 0.
4. Show changed screens on a preview page: capture each live and in this preview by /verify's plain checks at phone width (computer too if it differs), no --full-page, scout, save, or PR comment. Run node "$(git rev-parse --show-toplevel)/.claude/skills/apply/scripts/preview-review.mjs" "<change-name>" --pair "<title>|<live>|<preview>" --link (no live one for a new screen; --approved with the plan's After, or its live card at 390 and 1280 px, in place of live); report its link. None to show, or a capture fails → say why; keep the link and the choice.
5. Report and ask in plain words: what was built, what the review found and fixed, any can't-be-undone line, the preview link, each Check: bullet under Checks loosened (what is no longer checked, why), and unfixed files. Ask the next step with the question tool: publish it (Recommended) via /ship, change it more, or save via /save.

Repeat under the same alias for more edits; added tasks go to a new helper.

Work that changes no repo file

Work the conversation's numbered to-do in order, writing one if missing (verbs for any work). Only an outward step asks, showing exactly what it will do (recipient, full text, amount, target) in the shared ask format: one confirmation, one action, unless the person asked for a batch. Skip and report a declined step. Report without /save. Done → step-title.mjs set DONE.

Boundaries

• Git stays with /save, on either route; the preview upload is not git and gates nothing.
• Never save to stop or between parts (why), but for final acceptance.