vf-calibrate

Detect VibeFlow framework drift and plan approved lab migrations.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-calibrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vf-calibrate
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/conductor/skills/vf-calibrate
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill vf-calibrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects drift between the VibeFlow framework and an installed lab, helping teams handle framework changes without silently overwriting local structure, doctrine, or contextual rules.

Core Features & Use Cases

  • Version Drift Detection: Compares the framework version recorded in a lab with the current plugin version and distinguishes up-to-date, minor, and major changes.
  • Migration Planning: Classifies changes as bug fixes, new capabilities, or doctrine-breaking changes, then presents a reversible migration plan for human approval.
  • Controlled Recalibration: Creates a snapshot, refreshes affected modules, reaffirms MCP access, restamps framework metadata, and delegates a post-migration audit.
  • Use Case: When VibeFlow introduces a new planning structure or doctrine, use this Skill to identify planning debt, preserve existing work through promotion or archiving, and migrate the lab under explicit human validation.

Quick Start

Ask the skill to check whether the current lab is aligned with the installed VibeFlow framework and propose any required migration.

Frequently Asked Questions about vf-calibrate

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

FAQPage Schema
How do I detect version drift between a framework and my installed lab?

Version drift detection compares the framework version recorded in your lab with the current plugin version, distinguishing up-to-date, minor, and major changes to identify structural migration needs.

What is the best way to plan a framework migration without overwriting local doctrine?

Plan a controlled framework migration by classifying changes as bug fixes, new capabilities, or doctrine-breaking updates, then present a reversible migration plan for explicit human approval before proceeding.

How do I recalibrate a lab after a framework upgrade?

Lab recalibration creates a pre-migration snapshot, refreshes affected modules, reaffirms MCP allowlist access, restamps framework metadata, and delegates a post-migration audit to ensure safe realignment.

Does the migration process require human approval before applying changes?

Yes, controlled recalibration requires human approval before changes. The workflow preserves existing work through promotion or archiving and migrates the lab under explicit human validation.

When do I need to run a structural migration for my installed lab?

You need structural migration when VibeFlow introduces a new planning structure or doctrine, triggering session-start drift warnings that require module refreshes and version restamping to safely realign.

Can I preserve existing work when migrating to a new framework doctrine?

Yes, the migration workflow identifies planning debt and preserves existing work through promotion or archiving before applying any structural or doctrinal changes to the installed lab.