blueprint-migration

Solid

Versioned migration procedures for blueprint format upgrades (v1.x to v3.3). Use when blueprint-upgrade needs version-specific logic, content hashing, or rollback.

API & Backend 48 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Blueprint Migration Expert skill for migrating blueprint structures between format versions. This skill is triggered by `/blueprint:upgrade` and handles version-specific migration logic. ## When to Use This Skill | Use this skill when... | Use blueprint-upgrade instead when... | |---|---| | You need version-specific migration logic (v3.0→v3.1, v3.2→v3.3, etc.) | You're invoking the user-facing upgrade workflow with prompts | | You need content hashing to detect manual modifications during migration | You want the high-level "upgrade my blueprint" entry point | | You're implementing a new migration step between format versions | Use blueprint-init instead when the project has no manifest yet | ## Core Expertise - Reading and parsing the blueprint manifest (`docs/blueprint/manifest.json` in v3.0+, or legacy `.claude/blueprints/.manifest.json` in v1.x/v2.x) for current version - Determining appropriate migration path based on version comparison - Executing versioned migration steps with user confirmation - Content hashing for detecting manual modifications - Safe file moves with rollback capability ## Canonical Manifest Filename - **v3.0+**: `docs/blueprint/manifest.json` (canonical, no dot prefix — produced by `/blueprint:init`). Some repos carry a legacy `docs/blueprint/.manifest.json` from earlier v3.0 migrations; upgrade tooling tolerates both via the `$MANIFEST` variable resolved in `/blueprint:upgrade` Step 2. - **v1.x/v2.x (historical)**: `.claude/blueprints/.man...

Details

Author
laurigates
Repository
laurigates/claude-plugins
Created
7 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

blueprint-init

Initialize Blueprint Development structure. Use when bootstrapping docs/blueprint/ with manifest, PRD/ADR/PRP directories, and feature tracking for the first time.

48 Updated today
laurigates
API & Backend Listed

migration-playbook

Structured playbook for safely executing migrations: upgrading a major dependency version, framework migrations (e.g. React 17→18, Next.js 12→14, Vue 2→3), API deprecations, replacing one library with another, large-scale refactors touching many call sites, and database schema changes. Use this skill whenever the word "migrate", "upgrade", "deprecate", or "replace" applies to something with more than a handful of affected sites — even if it looks straightforward. Migrations that skip the inventory step consistently produce incidents from the sites nobody knew existed.

0 Updated today
sardonyx0827
Testing & QA Solid

blueprint-development

Generate project-specific rules from PRDs for Blueprint Development. Use when generating architecture, testing, or quality rules from requirements documents.

48 Updated today
laurigates