ifc-agents-file-validator

name	ifc-agents-file-validator
description	Use when asked to validate an IFC file, check whether an IFC model is conformant, run a pre-delivery quality gate on an IFC file, decide if an IFC file is valid, or triage a buildingSMART validation report. Prevents skipping the STEP-syntax gate, treating a warning as a file-invalidating error, reading a hidden pass as a skipped check, validating against the wrong schema, and confusing schema conformance with project information requirements. Covers the buildingSMART five-stage validation pipeline (STEP syntax, schema, normative, industry practice, bSDD), the Gherkin functional-part coverage map, the fifteen-item anti-pattern checklist, finding triage by severity, and routing each fault class to the matching ifc-errors skill, across IFC2x3, IFC4 and IFC4.3. Keywords: validate IFC file, is my IFC file valid, IFC validation pipeline, buildingSMART validation service, IFC conformance check, validation report triage, pre-delivery quality gate, schema validation, Gherkin normative rules, implementer agreement, informal proposition, industry practice warning, "is this IFC file ok", "how do I check an IFC file", "my IFC file failed validation", error vs warning, validation checklist, IFC quality gate, what makes an IFC file valid.
license	MIT
compatibility	Designed for Claude Code. Requires IFC IFC2x3, IFC4, IFC4.3.
metadata	{"author":"OpenAEC-Foundation","version":"1.0"}

IFC File Validator (Orchestration)

Drive a complete, ordered validation pass over an IFC file. This is an ORCHESTRATION skill : it sequences the buildingSMART five-stage validation pipeline, walks the fifteen-item anti-pattern catalog, triages every finding by severity, and routes each fault class to the matching ifc-errors-* skill that holds the detailed fix.

This skill answers one question : is this IFC file conformant, and if not, where is the fault and which skill fixes it. It does NOT itself teach the fixes. It is the conductor ; the ifc-errors-* skills are the instruments.

Scope boundary : this skill checks SCHEMA CONFORMANCE (the file obeys the IFC standard). It does NOT check PROJECT INFORMATION REQUIREMENTS (the file carries the data a specific project demanded). Information completeness beyond schema conformance belongs to ifc-agents-quality-checker. Project requirements are expressed in IDS, which is out of this package scope. For the conceptual validation MODEL see ifc-core-validation.

Quick Reference

The five-stage validation pipeline

The buildingSMART validation service runs these stages in order. ALWAYS run them in this order : a later stage assumes the earlier one passed.

Stage	Checks	Failure severity	Routes to
1. STEP Syntax	ISO 10303-21 file structure, header, string escaping	error : file rejected	ifc-errors-encoding-issues
2. Schema : version	schema id is IFC2X3, IFC4, or IFC4X3_ADD2	error	ifc-errors-version-mismatch
2. Schema : compliance	attribute types, cardinalities, inverse cardinalities, WHERE rules, global rules, abstract instantiation	error	ifc-errors-schema-validation
3. Normative : Implementer Agreements	ratified Gherkin normative rules	error	the fault-specific ifc-errors-* skill
3. Normative : Informal Propositions	mandatory rules not yet ratified	error	the fault-specific ifc-errors-* skill
4. Industry Practice	common-practice, sensible-default checks