speckit-upgradelisted

# SpecKit Upgrade ## Scope Upgrade an existing SpecKit installation in the current repository safely. Preserves `.specify/memory/constitution.md` and any other locally-modified files via backup-then-force-then-restore. Handles the v0.8.13 slash-command → skills migration. Supports upgrading one or both integrations (`claude`, `codex`). If `.specify/` is missing, hands off to `$speckit-install` — upgrade only operates on existing installs. This skill is **mutation-heavy** (it modifies files in `.specify/`, `.claude/`, `.codex/`, and writes backups to `/tmp/`). It runs only on explicit operator request and never auto-fires from other skills. ## Scope Boundaries — Not For - Initial install (no `.specify/` directory yet). That is `$speckit-install`. This skill hands off to it automatically. - Scaffolding a new spec from the technical roadmap. That is `$speckit-scaffold-spec`. - Installing this plugin's own bundled Codex subagent TOML files into `~/.codex/agents/`. That is `$install`. - Upgrading the SpecKit CLI binary itself (`specify` package). The operator runs that with `uv tool install --force` — this skill detects when it's out of date and recommends the command, but does not run it for them. ## Input Accept optional integration keys as arguments: - `$speckit-upgrade` (upgrade all installed integrations interactively) - `$speckit-upgrade claude` - `$speckit-upgrade codex` - `$speckit-upgrade claude codex` ## Hard Constraints - Always snapshot the repo