What problem does it solve? Migrating a legacy page to React without a fixed plan causes scope drift, missed behavioral variants, and gates that fail on correct code. This Skill turns a page's analysis.json and style-spec.json into a migration-plan.json that locks the component tree, rendering mode, required gates, and E2E scenarios before any code is generated. ## Core Features & Use Cases - Plan generation via migration-planner agent: Produces migration-plan.json with the React component tree, style targets, shared-package dependencies, rendering mode, required gates, 2-PR flag plan, and E2E scenario list. - Coverage reconciliation: Verifies every mustPreserve behavioral variant and copy source is either represented in the plan or recorded in openApprovals with a decision owner, preventing silent scope reductions. - State and safety guards: Refuses pages already flipped, done, or mid-flip, warns before demoting verified pages, and enforces lock files around tracker writes. - Use Case: After running fm-analyze and fm-style-spec on a hotel booking page, run this Skill to produce the migration plan that fm-gen will consume, with i18n language sets bound into the visual and E2E gate acceptance criteria. ## Quick Start Run /frontend-migration-plugin:fm-plan for my checkout page after fm-analyze and fm-style-spec have completed.
