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 directories. This Skill diagnoses those OutputPath and IntermediateOutputPath clashes in multi-project, multi-targeting, or multi-solution builds. ## Core Features & Use Cases - Binary log analysis: Queries .binlog files through MCP tools (evaluations, global properties, double writes) to find evaluations sharing output paths, with a text-log replay fallback when MCP is unavailable. - Root cause identification: Distinguishes clash causes such as missing AppendTargetFrameworkToOutputPath, shared BaseIntermediateOutputPath, extra global properties like PublishReadyToRun or _IsPublishing, and redundant SetTargetFramework metadata on ProjectReference. - Actionable fixes: Provides concrete MSBuild XML fixes for each cause, including path-neutral property detection and guidance on which evaluations to ignore (BuildProjectReferences=false P2P queries). - Use Case: A solution build fails randomly during NuGet restore with "Cannot create a file when that file already exists". Use this Skill to generate a binlog, compare IntermediateOutputPath across evaluations, and discover two projects share the same obj directory where project.assets.json is written. ## Quick Start Ask the AI to analyze the build binlog for projects with conflicting OutputPath or IntermediateOutputPath values causing the intermittent build failure.
