Skill

blueprint-migration

Migrates Claude Code blueprint structures between format versions (1.0.x to 3.1.0) via version-specific procedures, manifest updates, content hashing, and user-confirmed file operations.

Bash

Markdown

developer-tools

automation

npx claudepluginhub laurigates/claude-plugins --plugin blueprint-plugin

Tool Access

This skill is limited to using the following tools:

BashReadWriteEditGlobGrepAskUserQuestionTodoWrite

Preview

Expert skill for migrating blueprint structures between format versions. This skill is triggered by `/blueprint:upgrade` and handles version-specific migration logic.

Supporting Assets

migrations/v1.0-to-v1.1.mdmigrations/v1.x-to-v2.0.mdmigrations/v2.x-to-v3.0.mdmigrations/v3.0-to-v3.1.md

SKILL.md

Similar Skills

using-git-worktrees

169.2k

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

subagent-driven-development

169.2k

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

3 files

superpowers

dispatching-parallel-agents

169.2k

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

Stats

Parent Repo Stars23

Parent Repo Forks3

Last CommitFeb 27, 2026

Actions

View Source View Plugin View on GitHub View README

Blueprint Migration

Expert skill for migrating blueprint structures between format versions. This skill is triggered by /blueprint:upgrade and handles version-specific migration logic.

Core Expertise

Reading and parsing .claude/blueprints/.manifest.json 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

Migration Workflow

1. Read current manifest version
2. Compare with target version (latest: 3.1.0)
3. Load migration document for version range
4. Execute migration steps sequentially
5. Confirm each destructive operation
6. Update manifest to target version
7. Report migration summary

Available Migrations

From	To	Document
1.0.x	1.1.x	`migrations/v1.0-to-v1.1.md`
1.x.x	2.0.0	`migrations/v1.x-to-v2.0.md`
2.x.x	3.0.0	`migrations/v2.x-to-v3.0.md`
3.0.x	3.1.0	`migrations/v3.0-to-v3.1.md`

Version Detection

# Read manifest version - check both v3.0 and legacy locations
if [[ -f docs/blueprint/.manifest.json ]]; then
  cat docs/blueprint/.manifest.json | jq -r '.format_version'
elif [[ -f .claude/blueprints/.manifest.json ]]; then
  cat .claude/blueprints/.manifest.json | jq -r '.format_version'
fi

# Detect v1.0 (no format_version field)
if ! jq -e '.format_version' .claude/blueprints/.manifest.json > /dev/null 2>&1; then
  echo "v1.0.0"
fi

Content Hashing

For detecting modifications to generated content:

# Generate SHA256 hash of file content
sha256sum path/to/file | cut -d' ' -f1

# Compare with stored hash in manifest
jq -r '.generated.skills["skill-name"].content_hash' .claude/blueprints/.manifest.json

Migration Execution Pattern

When executing migrations:

Announce step - Explain what will happen
Check prerequisites - Verify source exists, target doesn't
Confirm with user - Use AskUserQuestion for destructive operations
Execute - Perform the migration step
Verify - Check operation succeeded
Update manifest - Track completion in manifest

Error Handling

If migration fails:

Stop immediately (fail-fast)
Report which step failed and why
Preserve original files (don't delete until confirmed)
Provide manual recovery instructions

Quick Reference

Operation	Command
Check version	`jq -r '.format_version' .claude/blueprints/.manifest.json`
Hash file	`sha256sum file \| cut -d' ' -f1`
Safe move	`cp -r source target && rm -rf source`
Check empty dir	`[ -z "$(ls -A dir)" ]`