Back to Prompt Library
implementation
Build the application
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Build a bSDD Real Estate Classification Compliance Checker
Format
Code-aware
Lines
86
Sections
11
Linked challenge
Build a bSDD Real Estate Classification Compliance Checker
Prompt source
Original prompt text with formatting preserved for inspection.
86 lines
11 sections
No variables
1 code block
## Build
Inspect Industry Foundation Classes models against the buildingSMART Data Dictionary standard. Verify mandatory classification references and provide gap reports for architectural submittals.
## User
BIM procurement coordinator
## Workflow
1. Ingest IFC property records and component classification references.
2. Query mock bSDD endpoints using classification code keys.
3. Compare model classifications against required project standards.
4. Render compliance audit cards highlighting unclassified assets.
## Interface
Web portal showing classification trees, matched dictionary terms, and missing requirement alerts.
## Data
Utilize sample bSDD dictionary responses available in open bSDD documentation or create local JSON mocks.
Starter examples below are synthetic. They are not downloaded records.
## Source
[IfcOpenShell](https://raw.githubusercontent.com/IfcOpenShell/IfcOpenShell/v0.8.0/README.md)
Leverages the bsdd library specification in IfcOpenShell to query classification references against data dictionaries.
## Tools
dspy, fastapi.
DSPy compiles robust prompt pipelines that accurately map arbitrary IFC classification text to standardized bSDD keys.
Local or cloud LLM supported by DSPy for semantic classification matching.
## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
## Acceptance
- Matches IFC element classifications to simulated bSDD dictionary URIs.
- Identifies elements lacking required standard classification codes.
- Generates non-blocking warnings for unmapped custom properties.
## Starter Examples
```json
[
{
"input": {
"model_id": "MOD-101",
"elements": [
{
"guid": "1abc",
"type": "IfcDoor",
"classification": {
"system": "OmniClass",
"code": "23-17 11 00"
}
}
]
},
"expected_output": {
"compliant": true,
"total_checked": 1,
"matched_entries": [
{
"guid": "1abc",
"system": "OmniClass",
"code": "23-17 11 00",
"uri": "https://identifier.buildingsmart.org/uri/omniclass/23-17-11-00"
}
],
"unresolved_elements": []
}
},
{
"input": {
"model_id": "MOD-102",
"elements": [
{
"guid": "2def",
"type": "IfcWindow",
"classification": null
}
]
},
"expected_output": {
"compliant": false,
"total_checked": 1,
"matched_entries": [],
"unresolved_elements": [
{
"guid": "2def",
"reason": "Missing classification reference"
}
]
}
}
]
```
## Safety
Read-only inspection of model metadata; no direct modification of original IFC files.
Use mock external writes. Require human review before any real deployment.Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Hold the task contract and output shape stable so generated implementations remain comparable.
Tune next
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Verify after
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.