home / skills / a5c-ai / babysitter / bim-clash-detection

This skill identifies and manages BIM coordination conflicts across disciplines, including hard, soft, and workflow clashes, and tracks resolutions.

npx playbooks add skill a5c-ai/babysitter --skill bim-clash-detection

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.6 KB
---
name: bim-clash-detection
description: BIM clash detection skill for identifying and managing coordination conflicts between disciplines
allowed-tools:
  - Read
  - Write
  - Glob
  - Grep
  - Edit
  - Bash
metadata:
  specialization: civil-engineering
  domain: science
  category: BIM Coordination
  skill-id: CIV-SK-014
---

# BIM Clash Detection Skill

## Purpose

The BIM Clash Detection Skill identifies and manages coordination conflicts between building disciplines including hard clashes, soft clashes, and workflow clashes.

## Capabilities

- Hard clash detection (physical interference)
- Soft clash detection (clearance violations)
- Workflow clash detection (sequencing)
- Clash grouping and prioritization
- Resolution tracking
- Report generation with visualization
- BCF format export
- Multi-model coordination

## Usage Guidelines

### When to Use
- Coordinating multi-discipline models
- Identifying design conflicts
- Managing clash resolution
- Documenting coordination issues

### Prerequisites
- BIM models available
- Coordination matrix defined
- Tolerance settings established
- Resolution workflow defined

### Best Practices
- Run regular detection cycles
- Prioritize clashes by impact
- Track resolution status
- Document resolutions

## Process Integration

This skill integrates with:
- BIM Coordination
- Shop Drawing Review

## Configuration

```yaml
bim-clash-detection:
  clash-types:
    - hard
    - soft
    - clearance
  tolerances:
    hard: 0
    soft: 50  # mm
    clearance: 100  # mm
  output-formats:
    - html
    - bcf
    - json
```

## Output Artifacts

- Clash reports
- BCF issue files
- Resolution logs
- Coordination matrices

Overview

This skill provides BIM clash detection to identify and manage coordination conflicts across building disciplines. It finds hard clashes, soft/clearance violations, and workflow sequencing issues, then groups and prioritizes them for resolution. Outputs include visual reports, BCF exports, and resolution logs to fit into coordination workflows.

How this skill works

The skill ingests multi-discipline BIM models and a coordination matrix, applies configured tolerances, and runs detection passes for hard, soft, and clearance clashes. It groups related issues, scores them by impact, and attaches resolution metadata as teams address items. Final artifacts include HTML/JSON reports, BCF issue files, and a tracked resolution log for audit and follow-up.

When to use it

  • During interdisciplinary coordination reviews and model federation sessions
  • Before construction to catch physical interferences and clearance problems
  • When validating sequencing or installation workflows for clashes
  • To generate BCF issue exports for contractors and consultants
  • As part of regular automated detection cycles during design iterations

Best practices

  • Define a clear coordination matrix and role responsibilities before runs
  • Set and document tolerances for hard, soft, and clearance checks
  • Automate regular detection cycles to catch regressions early
  • Prioritize clashes by schedule impact and constructability risk
  • Use BCF exports and visual reports to communicate with discipline leads

Example use cases

  • Detect pipe routing conflicts with structural framing and generate BCF issues for MEP and structure teams
  • Identify clearance violations around egress paths and prioritize fixes before permit submission
  • Run workflow clash checks to prevent overlapping installation sequences on-site
  • Generate coordinated clash reports for weekly coordination meetings and track resolutions

FAQ

What model formats are supported?

The skill works with common federated BIM exports; convert native files to supported exchange formats before ingestion.

How are clashes prioritized?

Clashes are grouped and scored by impact factors such as cost, schedule risk, spatial severity, and affected disciplines; teams can adjust weights in configuration.