mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-18 23:16:38 +03:00
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>* feat(migration-engineering): add migration-engineering skill Add the migration-engineering skill for safe cross-system migrations: schema, data, API, infrastructure, and service migrations. - SKILL.md: expand/contract pattern, compatibility windows, dual-running, backfills, reconciliation, cutover, deprecation, and cleanup. Four distinct recovery paths (rollback, roll-forward, restore, irreversible). Structured planning fields for reconciliation, correctness evidence, observability, customer impact, and ownership. Four migration types with detailed compatibility/correctness/recovery characteristics. Specialist routing to api-design-and-evolution, data-engineering, platform-engineering, release-engineering, site-reliability-engineering, implementation-planning, secure-software-engineering, qa-methodology, and verification-methodology. Prose routing to production-readiness and production-excellence. - README.md: human-facing overview with all five required sections. - references/discovery-brief.md: bounded survey of migration-adjacent skills and clear ownership boundaries. - references/compatibility-patterns.md: forward/backward compatibility by type. - references/recovery-classification.md: four recovery paths with decision tree. - templates/: migration plan, compatibility matrix, reconciliation plan, cutover and recovery record. - evals/evals.json: 5 output-quality cases covering additive schema change, backfill with reconciliation, API version migration, irreversible cutover, and reconciliation failure. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> * chore(migration-engineering): update catalogs and routing Regenerate catalog files and add migration-engineering entries to root README.md catalog and references/skill-triggers.md. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> --------- Co-authored-by: username <username> Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
39 lines
1.6 KiB
Markdown
39 lines
1.6 KiB
Markdown
# Compatibility Matrix Template
|
|
|
|
Build a compatibility matrix for a multi-consumer migration. Each row is a
|
|
consumer or dependency; each column is a migration phase.
|
|
|
|
## Matrix
|
|
|
|
| Consumer / Dependency | Current interface | Expand compatible? | Compatibility window status | Cutover ready? | Contract safe? | Notes |
|
|
|---|---|---|---|---|---|---|
|
|
| | | | | | | |
|
|
| | | | | | | |
|
|
| | | | | | | |
|
|
|
|
## Column definitions
|
|
|
|
- **Consumer / Dependency:** The system, service, team, or external partner
|
|
that depends on the interface being migrated.
|
|
- **Current interface:** What the consumer uses today (e.g., "REST v1
|
|
/orders", "Postgres orders table", "us-east-1 ECS cluster").
|
|
- **Expand compatible?:** Can this consumer continue to operate when the new
|
|
interface is added alongside the old? "Yes" means no action required from
|
|
the consumer during the expand phase. "No" means the consumer must take
|
|
action before or during expand.
|
|
- **Compatibility window status:** The consumer's progress toward migrating to
|
|
the new interface. Values: "Not started", "In progress (N% complete)",
|
|
"Migrated — monitoring", "Migrated — verified".
|
|
- **Cutover ready?:** Has this consumer verified that it works correctly with
|
|
the new interface and is prepared for the old interface to be removed?
|
|
- **Contract safe?:** Can the old interface be removed without breaking this
|
|
consumer? Must be "Yes" for all consumers before the contract phase.
|
|
- **Notes:** Contact person, migration deadline, special requirements, or
|
|
known issues.
|
|
|
|
## Consumer communication log
|
|
|
|
| Date | Consumer | Message | Response |
|
|
|---|---|---|---|
|
|
| | | | |
|