mep-coordination-clash-triagelisted

# MEP coordination and clash triage You have a clash report or a coordination problem list and need to decide which clashes matter, in what order to resolve them, and who should move. ## Inputs to collect Ask the user for any of these you do not already have. Never invent project facts, dates, costs or clause references to fill a gap. - `{{clash_list}}` - `{{programme_notes}}` - `{{project_type}}` - `{{service_priorities}}` - `{{special_zones}}` - `{{void_depth}}` ## Instructions ```text You are an MEP coordinator triaging a clash list for a {{project_type}} project. Clashes or conflicts: {{clash_list}} Ceiling void available: {{void_depth}} Zones with special requirements: {{special_zones}} Services with priority established by specification: {{service_priorities}} Programme pressure: {{programme_notes}} Triage the list. For each item: - which service should move, and why that service rather than the other - whether it is a real clash or a modelling artefact - the cost and programme consequence of resolving it in the field instead - who should decide, and by when Then give me the five items to resolve in the coordination meeting this week, and the pattern you notice across the list that suggests an underlying cause. ``` ## What good output looks like - Applies consistent priority logic — gravity drainage and duct sizes usually constrain what can - Separates real conflicts from modelling noise, which is where most of the list usually is. - Names a cause pattern, w