bp-skill-upgrade

Upgrade workflow.yaml files from older schema versions to v2.4+.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-skill-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-skill-upgrade
Source: https://github.com/hiivmind/hiivmind-blueprint/tree/main/skills/_archived/bp-skill-upgrade
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-skill-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

This skill should be used when the user asks to "upgrade workflow", "migrate workflow version", "update schema version", "fix deprecated types", "upgrade workflow.yaml", "modernize workflow", or needs to update a workflow.yaml from an older schema to v2.4+. Triggers on "upgrade", "migrate version", "update schema", "deprecated types", "modernize", "schema upgrade".

Frequently Asked Questions about bp-skill-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade a workflow.yaml from an older schema version to v2.4?

Upgrading a workflow.yaml involves detecting the current schema version, building an ordered migration plan, applying idempotent changes, and validating the upgraded workflow across schema, graph, types, and state.

What does schema migration idempotency mean for workflow.yaml files?

Idempotency during schema migration ensures that applying workflow.yaml upgrade changes multiple times yields the same result, preventing duplicate or corrupted data.

When do I need to migrate my workflow schema version?

You need to migrate your workflow schema version when fixing deprecated types, modernizing workflows, or upgrading workflow.yaml files to comply with the latest v2.4+ schema requirements.

Can I batch upgrade multiple workflow.yaml files at once?

Yes, you can batch upgrade eligible workflow.yaml files simultaneously, as the skill supports operating on a single file or a batch of files to apply schema migrations.

What is required to validate a workflow schema upgrade?

Validating a workflow schema upgrade requires up-to-date migration rules in patterns/migration-table.md and idempotency guards to verify the workflow across schema, graph, types, and state.

Are there limitations when fixing deprecated types in a workflow.yaml?

When fixing deprecated types, a limitation is that the skill requires up-to-date migration rules in patterns/migration-table.md; without them, the workflow.yaml schema upgrade cannot proceed accurately.