What problem does it solve? Package versions scattered across many .csproj, .fsproj, and .vbproj files are hard to govern, drift out of sync, and produce version conflicts. This Skill migrates .NET projects and solutions to NuGet Central Package Management (CPM), centralizing all package versions into a single Directory.Packages.props file. ## Core Features & Use Cases - Guided CPM conversion: Audits package references, resolves version conflicts with user input, creates Directory.Packages.props, and strips Version attributes from project files. - Baseline validation: Captures pre- and post-conversion builds with binlogs and JSON package lists to prove the conversion is version-neutral. - Structured report: Produces a shareable convert-to-cpm.md report with conflict resolutions, package comparison tables, risk assessment, and follow-up items such as security advisories. - Use Case: A team with 15 projects referencing different versions of System.Text.Json asks to align NuGet versions; the Skill audits the conflicts, centralizes versions, validates the build, and documents every change. ## Quick Start Convert my solution MyApp.sln to NuGet Central Package Management and generate a conversion report.