mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-12 20:16:29 +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>
2.8 KiB
2.8 KiB
Migration Plan Template
Fill this template for every migration that crosses a system boundary.
Migration identity
| Field | Value |
|---|---|
| Migration name | |
| Migration type(s) | Schema / Data / API / Infrastructure-Service |
| Current state | |
| Target state | |
| System boundary | |
| Risk class | Low / Medium / High |
Expand/Contract sequence
| Phase | Description | Duration | Gate |
|---|---|---|---|
| Expand | |||
| Compatibility window | |||
| Dual-running (if applicable) | |||
| Contract |
Backfill strategy (data migrations)
| Field | Value |
|---|---|
| Strategy | Full / Incremental / Streaming |
| Estimated volume | |
| Estimated duration | |
| Pre-conditions |
Reconciliation
| Field | Value |
|---|---|
| Strategy | Full / Incremental / Streaming |
| Frequency | Continuous / Hourly / Daily / Pre-cutover only |
| Coverage | All records / Statistical sample (size: ___) |
| Tolerance | |
| Failure action | Stop / Alert / Auto-reconcile |
Cutover procedure
| Step | Action | Pre-condition | Post-condition | Interruption point? |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| ... |
| Field | Value |
|---|---|
| Cutover window duration | |
| Acceptable downtime | |
| Abort trigger |
Recovery paths
| Migration step | Recovery classification | Procedure | RTO | Tested? |
|---|---|---|---|---|
Irreversible steps
| Step | Acceptance criteria | Stakeholder sign-off required | Contingency plan |
|---|---|---|---|
Correctness evidence
| Field | Value |
|---|---|
| Comparison method | Dual-read / Shadow-traffic / Consumer-side test / Synthetic validation |
| Pass criteria | |
| Evidence artifact |
Observability
| Field | Value |
|---|---|
| Progress metrics | |
| Anomaly signals | |
| Dashboards and alerts | |
| On-call rotation |
Customer impact
| Phase | Visible change | Downtime | Performance impact | Communication |
|---|---|---|---|---|
| Expand | ||||
| Compatibility window | ||||
| Cutover | ||||
| Contract |
Ownership
| Role | Name / Team | Accountable for |
|---|---|---|
| Migration lead | Overall plan and execution | |
| Expand phase owner | ||
| Dual-running phase owner | ||
| Cutover phase owner | ||
| Deprecation phase owner | ||
| Communication owner | Stakeholder and consumer notifications | |
| Escalation decision-maker | Pause, rollback, or abandon decisions |
Deprecation and cleanup
| Activity | Target date | Owner | Dependencies |
|---|---|---|---|
| Deprecation announcement | |||
| Consumer migration deadline | |||
| Old system read-only | |||
| Old system removal | |||
| Code/flag cleanup | |||
| Credential revocation |
Sign-off
| Role | Name | Date | Signature |
|---|---|---|---|
| Migration lead | |||
| (Irreversible steps only) Stakeholder |