What problem does it solve? When MSBuild performance summaries show ResolveProjectReferences consuming 50-80% of build time, developers often waste effort optimizing the wrong target. This Skill explains that the reported time is wall-clock wait time for dependent project builds, not actual CPU work, and redirects analysis to the real bottleneck. ## Core Features & Use Cases - Misleading Metric Detection: Confirms when ResolveProjectReferences appears as the top target in the Target Performance Summary and explains why the number is inflated by node-yield wait time (dotnet/msbuild#3135). - Task Self-Time Redirection: Guides users to the Task Performance Summary via the binlog MCP expensive_tasks tool, with a text-log replay fallback using dotnet msbuild and grep. - Bottleneck Routing: Points identified tasks (Csc, ResolveAssemblyReference, Copy) to the appropriate follow-up skills such as build-perf-diagnostics and build-parallelism. - Use Case: A developer sees ResolveProjectReferences taking 70% of a solution build. Instead of trying to optimize project references, they use this Skill to discover that Csc analyzer execution is the true bottleneck. ## Quick Start Analyze my build.binlog and tell me why ResolveProjectReferences dominates the Target Performance Summary and which task is the real bottleneck.
