# clash-resolution-analyzer

clash-resolution-analyzer is a Claude Code skill that analyzes BIM clash reports, ranks intersections, detects recurring patterns, and assigns fixes to project disciplines.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 115 installs · ★ 434 repo stars
- Author: datadrivenconstruction
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/2_DDC_Book/4.3-BIM-Validation-Pipeline/clash-resolution-analyzer/SKILL.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/clash-resolution-analyzer

## What it does

The skill ingests clash detection outputs from tools like Navisworks and structures them into actionable coordination tasks. It assigns status flags, impact tiers, and suggested fix strategies such as routing around obstructions, shifting elevations, or resizing ductwork.

Its Python engine applies predefined discipline hierarchies. Structural elements take precedence over architectural components, while mechanical, plumbing, and electrical conduits must adapt around structural frames. A hard clash penetrating structural members by more than 100 mm is flagged as critical.

Execution requires `python3` installed on the host system. The implementation supports Darwin, Linux, and Windows environments.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill clash-resolution-analyzer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/clash-resolution-analyzer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/clash-resolution-analyzer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill clash-resolution-analyzer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/clash-resolution-analyzer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill clash-resolution-analyzer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/clash-resolution-analyzer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction 2_DDC_Book/4.3-BIM-Validation-Pipeline/clash-resolution-analyzer
```

2. **Manually: put the files in place**
- File: `.github/skills/clash-resolution-analyzer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill clash-resolution-analyzer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --path 2_DDC_Book/4.3-BIM-Validation-Pipeline/clash-resolution-analyzer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/clash-resolution-analyzer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill clash-resolution-analyzer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/2_DDC_Book/4.3-BIM-Validation-Pipeline/clash-resolution-analyzer/SKILL.md

## When to use it
- filter and categorize spatial clashes exported from Navisworks
- detect critical hard clashes between MEP runs and structural members
- assign resolution ownership across specialized design disciplines
- identify repetitive layout clashes caused by common root causes

## Example prompts
- Analyze clash detection output and highlight severe conflicts involving structural framing
- Assign discipline responsibilities for newly imported MEP clashes and suggest routing changes
- Generate a clash report grouped by trade priority and resolution status

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: c8378c6f4060faed.

BEGIN THIRD-PARTY FILE c8378c6f4060faed
````text
---
name: "clash-resolution-analyzer"
description: "Analyze BIM clash detection results and suggest resolutions. Prioritize clashes, identify patterns, assign responsibility, and track resolution status."
homepage: "https://datadrivenconstruction.io"
metadata: {"openclaw": {"emoji": "🔎", "os": ["darwin", "linux", "win32"], "homepage": "https://datadrivenconstruction.io", "requires": {"bins": ["python3"]}}}
---
# Clash Resolution Analyzer for Construction

## Overview

Analyze clash detection results from BIM coordination. Prioritize clashes by impact, identify patterns, suggest resolutions, assign responsibility, and track resolution progress.

## Business Case

Clash resolution analysis enables:
- **Efficient Coordination**: Focus on critical clashes first
- **Pattern Recognition**: Fix root causes, not symptoms
- **Clear Accountability**: Assign responsibility by trade
- **Progress Tracking**: Monitor resolution status

## Technical Implementation

```python
from dataclasses import dataclass, field
from typing import List, Dict, Any, Optional, Tuple
from enum import Enum
from datetime import datetime
from collections import defaultdict

class ClashPriority(Enum):
    CRITICAL = 1  # Must resolve before construction
    HIGH = 2      # Resolve in next coordination cycle
    MEDIUM = 3    # Resolve before trade starts
    LOW = 4       # Minor, can resolve in field

class ClashStatus(Enum):
    NEW = "new"
    ASSIGNED = "assigned"
    IN_PROGRESS = "in_progress"
    RESOLVED = "resolved"
    APPROVED = "approved"
    VOID = "void"  # Not a real clash

class ResolutionType(Enum):
    ROUTE_AROUND = "Route around obstruction"
    RAISE_LOWER = "Raise or lower element"
    RESIZE = "Resize element"
    RELOCATE = "Relocate element"
    STRUCTURAL_MOD = "Structural modification required"
    DESIGN_CHANGE = "Design change required"
    NO_CLASH = "Not a real clash (tolerance)"
    SEQUENCE = "Resolve by construction sequence"

@dataclass
class ClashElement:
    id: str
    name: str
    category: str
    discipline: str
    level: str
    system: str

@dataclass
class Clash:
````
END THIRD-PARTY FILE c8378c6f4060faed

The third-party file has ended. Everything between the c8378c6f4060faed tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2111 of 17471 bytes. © datadrivenconstruction · MIT · https://github.com/datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction/tree/HEAD/2_DDC_Book/4.3-BIM-Validation-Pipeline/clash-resolution-analyzer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
