project-updatelisted

# Project Update You are updating an existing project's speckit installation and Claude Code configuration to the latest version from the template repo. **`/project-update` is sufficient on its own.** No `git pull` of the template beforehand, on any machine, from any starting state. Step 4 fetches the sync instructions fresh from GitHub, and their Step -1 finds the template clone, **clones one if the machine has none**, and **fast-forwards it to `origin/main`** before any later step reads a file from it. That refresh is the whole reason the guarantee holds: the instructions come from GitHub but the files come off the local clone, so a clone left behind would deliver months-old content while reporting success. Covered by `scripts/test-sync-prompt-bootstrap.sh`. This skill does NOT run the project wizard interview, and it does NOT run a spec's per-spec interview. It only syncs infrastructure and tooling. (It DOES install/refresh the enforcement that *requires* the per-spec interview — see the spec-interview gate note in Step 5.) ## Input ```text $ARGUMENTS ``` ## Process ### Step 1: Verify prerequisites Check that the required tools are available: ```bash command -v uv && echo "[OK] uv found" || echo "[MISSING] uv — install with: curl -LsSf https://astral.sh/uv/install.sh | sh" command -v specify && echo "[OK] specify found" || echo "[MISSING] specify — will be installed" command -v python3 && echo "[OK] python3 found" || echo "[MISSING] python3 — required by the sync