What problem does it solve? MSBuild builds fail intermittently with errors like "Cannot create a file when that file already exists" or "file is being used by another process" when multiple project evaluations write to the same bin/obj output directories. This Skill diagnoses those clashes by analyzing binary build logs. ## Core Features & Use Cases - Binlog-based clash detection: Queries a .binlog via MCP tools (evaluations, global properties, double_writes) to find evaluations sharing OutputPath or IntermediateOutputPath. - Root cause catalog: Covers multi-targeting without TargetFramework in path, shared BaseIntermediateOutputPath across projects, multi-solution builds, redundant global properties like PublishReadyToRun, and SetTargetFramework misuse. - Concrete fixes: Provides XML snippets for each cause, such as AppendTargetFrameworkToOutputPath, unique per-project obj paths, and RemoveGlobalProperties on ProjectReference. - Use Case: A CI build intermittently fails NuGet restore with "Cannot create a file when that file already exists". Use this Skill to inspect the binlog, discover two projects share the same IntermediateOutputPath where project.assets.json is written, and apply the per-project obj path fix. ## Quick Start Analyze my build.binlog file and tell me which MSBuild projects have conflicting OutputPath or IntermediateOutputPath values and how to fix them.
