/claims-defense

/cps-construction:claims-defense

Claims Defense. Analyze EOT/disruption claims using delay analysis methodologies (TIA, AACE 29R-03).

When to use

When the engagement scope explicitly calls for claims defense work in the construction & epc domain. Look for keywords like: construction, EPC, FIDIC, NEC, BIM.

Inputs you should gather first

• The engagement project.json (industry, service line, regulatory frameworks)
• Relevant client documents already ingested into the brain (run /cps:graph-query to find them)
• Any prior CPS Construction & EPC deliverables for cross-reference (central brain)

Steps

1. Read the engagement project.json and confirm scope includes Construction & EPC.
2. Load the construction skill (plugins/ind-construction/skills/construction/SKILL.md) and any matching industry skill.
3. Use the relevant subagent(s) — see Integration table below — to do the analysis.
4. Apply the methodology described in the skill, citing all sources.
5. Place the deliverable in 05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: construction-claims-defense-<client>-<YYYYMMDD>.md.
6. Run /cps:verify-quality before marking the workstream complete.

Output shape

A CPS-branded deliverable with:

• Pyramid-Principle structure (recommendation up front)
• Source citations on every data point
• Recommendation Format used in any advice section
• Quality bar items below all checked

Quality bar

• Project controls have baseline + actual + EAC + variance per work package
• BIM assessment cites ISO 19650 levels explicitly
• Schedule risk analysis uses Monte Carlo with named distributions