Skip to content

MIGRATION.md

Latest commit

 

History

History
46 lines (34 loc) · 2.35 KB

MIGRATION.md

File metadata and controls

46 lines (34 loc) · 2.35 KB
Raw

Migrate from older Blueprint skills

Breaking change: Blueprint now ships ten skills. You must remove old Blueprint skill folders and copied commands by hand.

What changed

Before Now
No previous equivalent /architecture
No previous equivalent /html-doc
multitask /codex-issue-coordinator for Codex issue batches
/issue-coordinator /codex-issue-coordinator
Design review through /review /architecture-review
design-doc, spec /design
browser-verify Browser proof inside /test
refactor /improve
branch, commit, implement, pr, pr-to-ready Steps inside /task-to-pr
task-to-pr /task-to-pr, now for one or more tasks
debug, tdd Techniques used while implementing
goal-design Ordinary instructions or a project-specific workflow
milestone /task-to-pr with the milestone as input
code-reviewer agent definition A fresh generic subagent launched by /review

These are the ten skills you can call:

/architecture · /design · /architecture-review · /plan · /test · /review · /improve · /task-to-pr · /html-doc · /codex-issue-coordinator

Clean upgrade

  1. Remove old Blueprint skills and commands. In the skill directory used by your coding tool, remove the old milestone skill and the other old Blueprint skill folders listed above. Also remove copied Blueprint implement.md and task-to-pr.md command files. Do not delete whole skill or command directories because they may contain unrelated files.

  2. Install all ten skills.

    npx skills add owainlewis/blueprint

  3. Remove copied reviewer agents. Delete any old Blueprint code-reviewer definition. The /review skill now launches a fresh generic subagent.

  4. Check the result. The /architecture, /design, /architecture-review, /plan, /test, /review, /improve, /task-to-pr, /html-doc, and /codex-issue-coordinator skills should be available.

Why cleanup is manual

Some update commands add or replace skills but do not remove folders from an older version. Running npx skills update alone can therefore leave both the old and new skills installed.

Use /task-to-pr to deliver one or more tasks. A GitHub milestone is one possible source of tasks. The skill creates one pull request for each task.