Skip to main content
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 Bilingual Commissioning Punch-List and Energy Defect Auditor

Format
Code-aware
Lines
65
Sections
11
Linked challenge
Build a Bilingual Commissioning Punch-List and Energy Defect Auditor

Prompt source

Original prompt text with formatting preserved for inspection.

65 lines
11 sections
No variables
1 code block
## Build
Extract and classify construction handover deficiencies from bilingual Arabic-English MEP inspection reports. Flag unresolved defects that impact building thermal performance and energy compliance.

## User
Handover documentation manager

## Workflow
1. Extract defect descriptions, inspection photos, and equipment tags from Arabic and English handover snag lists.
2. Map extracted deficiencies to EnergyPlus thermal zone and HVAC subsystem categories.
3. Score defect severity based on projected impact on building airtightness, chilled water flow, and electrical efficiency.
4. Generate a structured rectification notice in dual Arabic and English for subcontractor closeout remediation.

## Interface
A dual-column bilingual reviewer workspace displaying original punch items, automated categorization, and editable rectification drafts.

## Data
Construct 50 synthetic bilingual defect records in JSON format covering duct leakage, missing pipe insulation, and damper misalignments.
Starter examples below are synthetic. They are not downloaded records.

## Source
[EnergyPlus](https://raw.githubusercontent.com/NREL/EnergyPlus/develop/README.md)
Links commissioning defects to standard EnergyPlus HVAC and thermal envelope boundary components.

## Tools
mastra-ai, pydantic, fastapi.
Provides modular agent workflow orchestration and structured schema handling for bilingual text parsing and defect scoring.
Hosted multilingual model with demonstrated fluency in modern standard Arabic engineering terminology.

## 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
- Processes dual-language submittals and maps Arabic MEP terminology into standardized MasterFormat deficiency codes.
- Correctly flags missing chilled water pipe insulation as high thermal severity causing energy penalty.
- Produces valid bilingual rectification letters containing contractor tags, timeline for remediation, and re-inspection criteria.

## Starter Examples
```json
[
  {
    "input": {
      "item_id": "SNAG-402",
      "description_ar": "تسريب هواء ملحوظ عند وصلة مجرى الهواء الرئيسية في غرفة مناولة الهواء رقم 3",
      "description_en": "Noticeable air leakage at main duct connection in AHU room 03",
      "trade": "HVAC Ductwork",
      "zone": "Level 2 North"
    },
    "expected_output": {
      "energy_impact_level": "High",
      "affected_system": "ZoneInfiltration/DuctAirDistribution",
      "requires_retesting": true,
      "contractor_deadline_days": 3
    }
  },
  {
    "input": {
      "item_id": "SNAG-405",
      "description_ar": "غطاء لوحة التحكم الخاصة بمضخة المياه المثلجة غير محكم الإغلاق",
      "description_en": "Control panel enclosure latch for chilled water secondary pump is loose",
      "trade": "Electrical Controls",
      "zone": "Basement Plant Room"
    },
    "expected_output": {
      "energy_impact_level": "Low",
      "affected_system": "GeneralElectricalEnclosure",
      "requires_retesting": false,
      "contractor_deadline_days": 7
    }
  }
]
```

## Safety
Assists documentation review only. Physical site inspection and safety sign-offs remain the responsibility of certified site engineers.
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.