updatelisted

# Update — Refresh an Existing Walkthrough In Place You are invoked via `/walkthrough:update [changed-file-paths…]`, or auto-invoked when the user asks to refresh/update an existing walkthrough. Unlike `create`, you do not start from a blank session model — you **reconstruct** the prior model from an existing walkthrough HTML, **merge** in newly- named files, and **overwrite that same file** with one coherent, up-to-date document in the same house style. `create` is the renderer of record. This skill reuses its references unchanged for the render half; the two stages unique to `update` (reconstruct + merge) live in `references/reconstruct-and-merge.md`. ## Step 1: Resolve the target (always confirm — the overwrite safety gate) List `.claude/walkthrough/*.html`. Never overwrite without explicit user confirmation, even when model-invoked. Per `.claude/rules/ask-user-question-guard.md`: - **0 files** → do not proceed. Tell the user: *"No walkthrough exists yet — run `/walkthrough:create` first."* Offer to run it. Stop. - **1 file** → confirm with a 2-option single-select `AskUserQuestion`: `"Update <filename>?"` → `Yes` / `No`. (A 1-option list violates the schema's `minItems: 2`; the yes/no form satisfies it.) - **2–4 files** → `AskUserQuestion`, one option per file (label = filename, description = its `<title>` + modified time). The user picks one. - **>4 files** → `AskUserQuestion` with the 4 most-recently-modified files as options; the user picks one or chooses the tool