blueprint-upgradelisted

Upgrade the blueprint structure to the latest format version. ## When to Use This Skill | Use this skill when... | Use blueprint-init instead when... | |---|---| | The project has a manifest at v1.x, v2.x, v3.0, v3.1, or v3.2 | The project has no `docs/blueprint/manifest.json` at all | | You want the user-facing upgrade entry point with prompts | Use blueprint-migration instead when implementing version-specific logic | | You're adding the v3.2 task registry or v3.3 monorepo workspaces | Use blueprint-execute instead when you want auto-detection of next step | | You're running batch upgrades across repos with `--non-interactive`/`-y` | Use blueprint-status instead to first audit current version | **Current Format Version**: 3.3.0 This command delegates version-specific migration logic to the `blueprint-migration` skill. ## Parameters Parse `$ARGUMENTS` for flags before running any step: - `--non-interactive`, `--yes`, `-y`: Skip every `AskUserQuestion` prompt and apply the defaults in the table below. Intended for batch runs across many repos (e.g. looping `/blueprint:upgrade -y` over FVH repos that are already on `main`). Set an internal `$NONINTERACTIVE` flag to `true` when any of those tokens appear in `$ARGUMENTS`; otherwise `false`. Reference this flag at every `AskUserQuestion` call site in the steps below. ### Non-interactive defaults When `$NONINTERACTIVE` is `true`, use these answers without prompting and record them in `upgrade_history[].changes` as "auto-