What problem does it solve? Large-scale refactoring efforts often fail because changes are made without a plan, phases are mixed into single commits, and verification is skipped. This Skill enforces a disciplined lifecycle for engineering-grade refactoring: produce a plan document, get approval, execute phase by phase, verify each phase independently, and commit each phase separately. ## Core Features & Use Cases - Stack-Based Routing: Detects project signals (.sln, .csproj, .razor, Blazor) and routes .NET/C#/Blazor work to ada-dotnet-engineering-refactoring, while other stacks route to the language-agnostic ada-engineering-refactoring skill. - Phased Execution Lifecycle: Requires a plan document in docs/refactoring/ with quality standards, phase goals, change lists, verification criteria, and dependency diagrams before any code changes begin. - Independent Phase Verification: Mandates dotnet build, dotnet test, and dotnet format after every phase, with isolated git commits per phase for bisectability. - Use Case: A user says their Blazor component library does not meet engineering standards and wants a staged architecture upgrade covering domain primitives, orchestrator extraction, and public API stabilization. The Skill routes to the .NET sub-skill and enforces the plan-then-execute workflow. ## Quick Start Ask the agent to plan an engineering-grade, multi-phase refactoring of your project and it will route to the correct stack-specific skill before proposing any changes.
