bp-maintain

Diagnose and migrate YAML workflow definitions with idempotent safeguards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the diagnosis, validation, upgrade, and refactor of YAML-based workflow definitions, consolidating multi-dimension checks and migrations into a single, repeatable process.

Core Features & Use Cases

  • Diagnose schema, graph, type, state, and blueprint health for a given workflow.
  • Plan and apply safe, idempotent migrations (2.0 to 2.4) with backup and rollback safeguards.
  • Refactor workflows by extracting subflows, splitting, renaming nodes, or cleanup of dead code.

Quick Start

Run bp-maintain on a workflow to diagnose issues and apply safe upgrades or refactors.

Frequently Asked Questions about bp-maintain

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

FAQPage Schema
How do I validate and diagnose issues in a YAML workflow definition?

To validate a YAML workflow, you diagnose its schema, graph structure, types, state, and blueprint health. This process identifies structural issues and configuration problems, providing actionable recommendations to ensure correctness and longevity across complex workflow graphs.

What is the best way to refactor a complex YAML workflow graph?

Refactoring a complex YAML workflow graph involves extracting subflows, splitting nodes, renaming components, and cleaning up dead code. This process simplifies complex definitions while maintaining idempotent safeguards to prevent breaking existing state or blueprint integrity during structural modifications.

How do I migrate a workflow definition to a newer version safely?

Migrating a workflow definition to a newer version requires applying idempotent migrations with backup and rollback safeguards. You can safely upgrade YAML workflows across versions, such as 2.0 to 2.4, while validating schema and state to ensure the graph remains functional and correct.

Can I upgrade a single workflow without affecting other graphs in my project?

Yes, you can perform single-workflow maintenance tasks such as validation, migration, and refactoring independently. The process applies idempotent safeguards with backup and rollback capabilities, ensuring that upgrading or diagnosing one complex graph does not impact other workflow definitions in your project.

What does workflow blueprint validation check for during a diagnosis?

Workflow blueprint validation checks the schema, graph connections, type consistency, and state integrity of a YAML workflow definition. It diagnoses overall health by identifying dead code, structural errors, and configuration mismatches, then provides actionable recommendations to resolve them.