Construction: RFI And Submittal Review with Claude Code: API Runtime Pattern
A production playbook for RFI and submittal review in construction operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Construction project teams
The problem
Construction project teams need RFI and submittal review to run repeatedly against RFIs, submittals, drawings, specs, change orders, and project notes. In construction operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the RFI and submittal review instructions as a skill, send RFIs, submittals, drawings, specs, change orders, and project notes as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For RFI and submittal review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=construction-rfi-submittal-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo