Agent Blueprint
Get started
Browse the pages

DocsGet started

Upgrade from v3

Moving from v3 (claude-code-blueprint) means installing v4, running the ab-migrate skill in each project, removing the old plugin and learning the new ab- skill names. The upgrade guide on GitHub has the full name map, what moved where and how to roll back:

  1. Install v4 for your tools, as described in Install. In Claude Code the new plugin is agent-blueprint@agent-blueprint; the old claude-code-blueprint@claude-code-blueprint stays installed until step 3, and the v4 session-start hook reminds you until then. install.sh --legacy, which copied v3 into a project’s .claude/, is retired and points you at ab-migrate.

  2. Clean each project with ab-migrate. Open a session in a project that used v3 and name the skill (it is manual-only). It lists what v3 left there: in-project copies of skills, agents and hooks, scripts/ship.sh, ship state under .claude/, and a CLAUDE.md that should become AGENTS.md. It asks once, removes only the files the blueprint installed, behind a blueprint-v3-backup branch, and makes no commit, so you review the diff and commit it yourself.

  3. Remove the v3 plugin once no project needs the old skills:

    claude plugin uninstall claude-code-blueprint@claude-code-blueprint
claude plugin marketplace remove claude-code-blueprint

  4. Refresh the project files. Run ab-project-start in the migrated project. It adds the v4 files the project lacks and keeps every section your AGENTS.md already has.

  5. Use the new names. /build-pipeline is now ab-build-pipeline, and the other skills gained the same prefix. The exceptions are agent-teams and team-execution, which merged into ab-orchestrate, and migrate-to-plugin, which became ab-migrate. The full map, the folder changes and what happened to each v3 instruction rule are in docs/upgrade/v4.md.