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.
Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026
Voraussetzungen
Add the project RFI form, numbering convention, and response statuses. Define the evidence standard for schedule and cost impact estimates. Specify required distribution roles and response-time conventions. Add project rules for urgent field conditions.
Skill-Dokument
Das vollständige SKILL.md, das dein Agent liest und befolgt.
Construction RFI draft
Purpose
Create an RFI that gives the responsible design or project party enough context to answer a field question without repeated clarification.
Scope
Questions arising from plans, specifications, site conditions, interfaces, or constructability. Excluded: sending the RFI, deciding the design solution, or authorizing changed work.
Data basis
- Observation or question, drawings, specifications, addenda, field notes, contract requirements, and RFI register.
- The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.
Result
A draft RFI, option and impact note, and a proposed register row.
Quality criteria
- The question identifies the exact location, document reference, and affected scope.
- The draft separates observed facts, requested clarification, and proposed options.
- Potential schedule, cost, quality, or safety effects are stated with evidence or marked unknown.
- Every cited plan or specification reference is valid and specific.
- The register row has a unique draft identifier and status.
Instructions
Write one decision question per RFI unless several issues cannot be separated. Describe the conflict without assigning blame. Include only options supported by the project documents or field facts. Do not treat a suggested option as an instruction. Flag safety-critical or schedule-critical implications explicitly and preserve all assumptions.
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.
- Add the project RFI form, numbering convention, and response statuses.
- Define the evidence standard for schedule and cost impact estimates.
- Specify required distribution roles and response-time conventions.
- Add project rules for urgent field conditions.
Verwandte 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 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.
- 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.