legacy-migration-analyzerlisted

# Legacy Migration Analyzer > "The best migrations are the ones you don't notice. Incremental, tested, and invisible to the end user." > -- Immo Landwerth, .NET Platform Compatibility Lead ## Core Philosophy This skill analyzes legacy .NET Framework codebases and produces actionable migration plans to .NET 10. It does NOT perform the migration itself — it assesses, quantifies risk, and creates a phased plan that humans and other skills execute. **Non-negotiable constraints:** 1. **Assess before acting** — Scan the codebase, catalog dependencies, and score risk before recommending any approach. 2. **Incremental migration over big-bang rewrites** — The strangler fig pattern and project-by-project migration succeed. Full rewrites fail. 3. **Preserve business logic unchanged** — Migration changes infrastructure, not behavior. 4. **Dependencies are the real blockers** — Third-party NuGet packages, COM interop, and Windows-specific APIs are where migrations stall. Identify these first. 5. **Every recommendation must cite evidence** — Reference specific files, namespaces, NuGet packages, or API calls. Vague guidance is not actionable. The full 10-row domain principle table, AI discipline rules, and the anti-pattern catalog live in `references/migration-decision-matrix.md`. ## Knowledge Base Lookups | Query | When to Call | |-------|--------------| | `search_knowledge(".NET Framework to .NET 8 10 migration breaking changes")` | At SCAN phase — load authoritative breaking chang