mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-15 05:26:28 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
18f78a1c20
Body was ~20.5k chars, past the new 20k token-budget gate. Moves the five migration-type classifications into references/migration-types.md and the structured planning field tables into references/planning-fields.md (cross-referencing templates/migration-plan.md). SKILL.md keeps triggers, boundaries, the workflow skeleton with summaries pointing at existing references, the Loading Guide (now including both new files), and specialist routing; body is now 11,432 chars. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
52 lines
2.2 KiB
Markdown
52 lines
2.2 KiB
Markdown
# Structured Planning Fields
|
|
|
|
Load this file when drafting or reviewing a migration plan: every plan must
|
|
address these fields. They may appear as checklist items, template fields,
|
|
table columns, or labeled section headers — not only as prose. The
|
|
[`../templates/migration-plan.md`](../templates/migration-plan.md) template
|
|
provides the ready-made structure that instantiates these fields.
|
|
|
|
## Reconciliation
|
|
|
|
| Field | Question to answer |
|
|
|---|---|
|
|
| Strategy | Full, incremental, or streaming reconciliation? |
|
|
| Frequency | Continuous, hourly, daily, or pre-cutover only? |
|
|
| Coverage | All records or a statistical sample? |
|
|
| Tolerance | What divergence is acceptable? |
|
|
| Failure action | Stop, alert, or automatically re-reconcile? |
|
|
|
|
## Correctness evidence
|
|
|
|
| Field | Question to answer |
|
|
|---|---|
|
|
| Comparison method | Dual-read, shadow-traffic, consumer-side test, or synthetic validation? |
|
|
| Pass criteria | What measurements confirm correctness (e.g., "100% record match," "error rate < 0.01%," "p95 latency within 10% of baseline")? |
|
|
| Evidence artifact | Where is the evidence recorded (dashboard link, test report, reconciliation log)? |
|
|
|
|
## Observability
|
|
|
|
| Field | Question to answer |
|
|
|---|---|
|
|
| Progress metrics | Bytes migrated, records processed, consumers cut over? |
|
|
| Anomaly signals | Error-rate spikes, latency degradation, reconciliation drift? |
|
|
| Dashboards and alerts | Where are migration-specific metrics visible, and who is on-call? |
|
|
|
|
## Customer impact
|
|
|
|
| Field | Question to answer |
|
|
|---|---|
|
|
| Visible change | What does the customer experience during each phase? |
|
|
| Downtime | Is any downtime expected, and how is it communicated? |
|
|
| Performance | Could latency, throughput, or error rates change during the migration? |
|
|
| Support | How are customer issues triaged and escalated during the migration window? |
|
|
|
|
## Ownership
|
|
|
|
| Field | Question to answer |
|
|
|---|---|
|
|
| Migration lead | Who owns the overall migration plan and its execution? |
|
|
| Phase owners | Who is accountable for expand, dual-running, cutover, deprecation, and cleanup? |
|
|
| Communication owner | Who owns stakeholder and consumer notifications? |
|
|
| Escalation path | Who is the decision-maker if the migration must be paused, rolled back, or abandoned? |
|