What problem does it solve? When analyzing .NET build performance, ResolveProjectReferences often appears as the most expensive target in the Target Performance Summary, leading developers to waste effort optimizing a target that is mostly idle wait time for dependent project builds rather than real CPU work. ## Core Features & Use Cases - Misleading Metric Detection: Confirms when ResolveProjectReferences dominates the Target Performance Summary and explains why the number reflects node-yield wait time (dotnet/msbuild#3135), not actual work. - Task Self-Time Redirection: Guides analysis to the Task Performance Summary using the binlog MCP expensive_tasks tool, with a text-log replay fallback via 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 consuming 60% of build time in a binlog and is about to optimize it; this Skill explains the metric is misleading and helps identify Csc analyzer time as the true bottleneck. ## Quick Start Analyze my build.binlog where ResolveProjectReferences appears as the most expensive target and tell me what the real bottleneck is.
