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 an IFC 4D Construction Task Sequence Synchronizer
Format
Code-aware
Lines
95
Sections
11
Linked challenge
Build an IFC 4D Construction Task Sequence Synchronizer
Prompt source
Original prompt text with formatting preserved for inspection.
95 lines
11 sections
No variables
1 code block
## Build
Correlate IFC architectural components with construction schedules using ifc4d conventions. Identify elements missing work package assignments and flag schedule sequence anomalies.
## User
Construction project scheduler
## Workflow
1. Upload IFC structural files alongside Gantt schedule task arrays.
2. Link IFC element identifiers to scheduled construction tasks.
3. Verify task predecessors and detect unscheduled structural elements.
4. Generate 4D synchronization logs for project superintendent review.
## Interface
Split-pane web view displaying Gantt timeline on the left and IFC entity schedule matrix on the right.
## Data
Use open-source synthetic IFC models combined with standard CSV task schedules.
Starter examples below are synthetic. They are not downloaded records.
## Source
[IfcOpenShell](https://raw.githubusercontent.com/IfcOpenShell/IfcOpenShell/v0.8.0/README.md)
Applies the ifc4d module referenced in IfcOpenShell to link IFC entities with project management timelines.
## Tools
mastra-ai, fastapi.
Mastra AI provides deterministic workflow orchestration to trace entity-to-task relationships and schedule states.
Local or hosted LLM with fast structured JSON output for linking descriptions to tasks.
## 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
- Links IFC component GUIDs to scheduled task IDs.
- Flags structural elements lacking corresponding task assignments.
- Highlights chronological dependencies where tasks precede element prerequisites.
## Starter Examples
```json
[
{
"input": {
"tasks": [
{
"task_id": "T1",
"name": "Pour Footings",
"start": "2025-04-01",
"end": "2025-04-05"
},
{
"task_id": "T2",
"name": "Erect Columns",
"start": "2025-04-06",
"end": "2025-04-10"
}
],
"elements": [
{
"guid": "col-01",
"type": "IfcColumn",
"task_id": "T2"
}
]
},
"expected_output": {
"synchronized": true,
"assigned_elements": 1,
"unassigned_elements": [],
"schedule_alerts": []
}
},
{
"input": {
"tasks": [
{
"task_id": "T1",
"name": "Pour Footings",
"start": "2025-04-01",
"end": "2025-04-05"
}
],
"elements": [
{
"guid": "col-02",
"type": "IfcColumn",
"task_id": null
}
]
},
"expected_output": {
"synchronized": false,
"assigned_elements": 0,
"unassigned_elements": [
"col-02"
],
"schedule_alerts": [
"Element col-02 has no assigned construction task."
]
}
}
]
```
## Safety
Simulates schedule linkages; does not issue live contractor dispatch orders or change construction site operations.
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.