Generate a governed migration packet capturing compatibility, sequencing, and fallback posture.
npx skills add https://github.com/apply-the/canon --skill canon-migration
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
Migrate existing systems with a governed, auditable packet that captures compatibility constraints, sequencing rules, and fallback posture to reduce risk and ensure traceability.
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>).
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
archibateApply controlled breaking changes to software artifacts and generate migration notes.
KentoShimizuDefine and enforce provider-consumer compatibility policies in CI.
apply-theCompose a governed supply-chain packet with SBOM, vulnerability, license, and legacy evidence.
cornmanwtfPlan monolithic to microservices migration with service boundaries and strangler strategies.
