What problem does it solve? Multi-project .NET solutions often build sequentially or leave CPU cores idle because MSBuild defaults to a single worker node, and long dependency chains create bottlenecks that are hard to see without analysis. ## Core Features & Use Cases - Parallelism Configuration: Guides correct use of -m /maxcpucount, graph build mode (/graph), and BuildInParallel on the MSBuild task. - Dependency Graph Optimization: Reduces unnecessary ProjectReference entries, applies solution filters (.slnf), and identifies critical-path bottlenecks. - Binlog-Based Diagnosis: Uses the binlog MCP server tools (expensive_projects, expensive_targets, project_target_times) with a text-log replay fallback to find slow projects and targets. - Use Case: A CI pipeline builds a 60-project solution in 20 minutes despite a multi-core runner; this Skill identifies that -m was missing and that one 60-second project blocks the critical path. ## Quick Start Analyze my solution's build.binlog and tell me why the build is not using all CPU cores and how to speed it up.