canon-migration

Generate a governed migration packet capturing compatibility, sequencing, and fallback posture.

1|Updated Mar 26, 2026

Search Tags:#compatibility #migration #evidence #ai-assistant #risk #packet #governed

Ready to run

npx skills add https://github.com/apply-the/canon --skill canon-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canon-migration
Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-migration
Command: npx skills add https://github.com/apply-the/canon --skill canon-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate existing systems with a governed, auditable packet that captures compatibility constraints, sequencing rules, and fallback posture to reduce risk and ensure traceability.

Core Features & Use Cases

Expose Canon's migration workflow as a governed run started from your AI assistant.
Bind risk, zone, and authored inputs to persist migration artifacts and evidence.
Reuse canonical migration briefs or inline notes to drive consistent decision making.

Quick Start

Author a migration brief at canon-input/migration/brief.md describing current state, target state, and risk, then invoke Canon with canon run --mode migration --system-context existing --risk <RISK> --zone <ZONE> [--owner <OWNER>] (--input <INPUT_PATH> | --input-text <INPUT_TEXT>).

Frequently Asked Questions about canon-migration

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

FAQPage Schema

How do I generate a governed migration packet for existing systems from an AI assistant?▼

To generate a governed migration packet, author a migration brief or inline note specifying current and target states, then invoke Canon with risk, zone, and input parameters to capture compatibility constraints, sequencing rules, and fallback posture.

What is a governed migration packet and when do I need one for system compatibility?▼

A governed migration packet is an auditable artifact that captures compatibility constraints, sequencing rules, and fallback posture for existing systems. You need one when a bounded migration surface requires formalized evidence and a reproducible run-start to reduce risk.

What inputs are required to start a governed migration run?▼

Starting a governed migration run requires a risk level, a zone, and at least one authored input, which can be a migration brief, a migration input folder, or inline notes. These inputs bind to the workflow to persist migration artifacts and evidence.

Can I use inline notes instead of a formal migration brief to drive migration decision making?▼

Yes, you can use inline notes instead of a formal migration brief. The workflow accepts inline notes, migration input folders, or authored briefs as valid input sources to drive consistent decision making and generate the migration packet.

How do I persist migration artifacts and evidence during a system migration?▼

You persist migration artifacts and evidence by binding risk, zone, and authored inputs through the governed migration workflow. This process formalizes compatibility, sequencing, and fallback posture into a reproducible, auditable packet.

What's the best way to ensure traceability and reduce risk during a bounded system migration?▼

The best way to ensure traceability and reduce risk is to generate a governed migration packet that captures compatibility constraints, sequencing rules, and fallback posture, providing formalized evidence and a reproducible run-start from your AI assistant.