writing-migration-plans

What problem does it solve? Migration and implementation plans often stall mid-run because phases are ordered by topic rather than by what blocks, scattering human gates across the whole run and leaving cleanup steps permanently deferred. ## Core Features & Use Cases - Two-deliverable discipline: Keeps the design doc limited to end state and rationale while the plan lives only in an append-only tracking issue, never a repo document. - Three-block ordering: Sorts every step into out-of-band setup, a single collapsed review gate over a full PR stack, and a chain of queued execution links armed on each other. - Failure-resilient chaining: Files each execution step as a sub-issue with Blocked-by edges, predicted diff scopes, automerge policies, and validation-on-read so the chain survives parked PRs, red CI, or unmerged closes. - Use Case: When about to write a DESIGN.md or phased rollout plan, use this to draft the plan, get owner approval of its shape, and file the entire chain of issues before any work starts. ## Quick Start Ask the AI to draft a migration plan for your initiative following this skill, producing a tracking issue with phases, a dependency graph, and per-link automerge policies before filing any issues.