Back to library

Construction punch list

Converts inspection notes, photos, room data, and project requirements into a prioritized construction punch list with trade grouping and verification fields. Use for substantial completion, handover inspections, snagging, closeout walks, and defect follow-up.

by adlass TemplatesVersion 1Uses adlass toolsUniversal

Published Aug 21, 2026 · Updated Aug 26, 2026

Helpful · 0View raw SKILL.md

Requirements

Add the project room or asset register and closeout criteria. Define priority classes and trade vocabulary. Set photo and drawing citation conventions. Specify verification roles and required evidence for closure.

Skill document

The full SKILL.md your agent reads and follows.

Construction punch list

Purpose

Create a complete, location-specific list of outstanding work that can be tracked from discovery through verification.

Scope

Visible construction defects, incomplete work, missing items, and closeout observations. Excluded: physical inspection, repair execution, and final acceptance.

Data basis

  • Walkthrough notes, photo folder, room or asset register, specifications, drawings, prior punch list, and closeout criteria.
  • The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

Result

A punch-list sheet, trade-grouped work-order brief, and verification schedule.

Quality criteria

  • Every item has a location, description, evidence reference, trade, and status.
  • Items are deduplicated without losing evidence.
  • Priority follows the project acceptance rules and explains safety or handover impact.
  • Work packages preserve the original punch-list identifiers.
  • Verification criteria are specific enough to determine closure.

Instructions

Describe the observable condition, not the presumed cause. Use room, grid, elevation, equipment, or asset identifiers consistently. Separate incomplete work from defective work and documentation gaps. Group items for execution only after preserving individual records. Do not mark items closed based on a proposed remedy; closure requires the defined evidence.

Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence. Keep closeout evidence tied to each item throughout the review.

  • Add the project room or asset register and closeout criteria.
  • Define priority classes and trade vocabulary.
  • Set photo and drawing citation conventions.
  • Specify verification roles and required evidence for closure.

Related skills

  • 8D problem-solving report

    Builds a traceable 8D problem-solving report from a manufacturing complaint, defect record, and process evidence. Use for customer complaints, recurring production defects, containment records, corrective action reports, and structured root-cause investigations.

  • Capacity resource plan

    Converts demand forecasts, staffing calendars, work hours, absences, and throughput assumptions into a capacity plan with bottleneck dates and quantified staffing options. Use for workforce capacity planning, resource allocation, utilization review, and delivery-load analysis.

  • Construction RFI draft

    Converts a construction field question or document conflict into a precise request for information with evidence, options, and schedule or cost implications. Use for RFIs, design clarifications, plan conflicts, specification gaps, and field coordination questions.

  • Contract price compliance

    Checks supplier invoice and purchase-order prices against signed contracts, item masters, discount schedules, and indexation clauses, quantifying overcharges and credits with clause and line citations. Use for procurement price audits, supplier recovery reviews, and contract compliance checks.