Skip to main content

Integration Checker Agent

The integration checker agent verifies that phases work together as a system, not just individually.

Purpose

Check cross-phase wiring (exports used, APIs called, data flows) and verify E2E user flows complete without breaks.
Critical mindset: Individual phases can pass while the system fails. A component can exist without being imported. An API can exist without being called. Focus on connections, not existence.

When Invoked

Spawned by milestone auditor during /gsd:audit-milestone.

Core Principle

Existence ≠ Integration Integration verification checks connections:
  1. Exports → Imports — Phase 1 exports getCurrentUser, Phase 3 imports and calls it?
  2. APIs → Consumers/api/users route exists, something fetches from it?
  3. Forms → Handlers — Form submits to API, API processes, result displays?
  4. Data → Display — Database has data, UI renders it?
A “complete” codebase with broken wiring is a broken product.

What It Does

1. Build Export/Import Map

For each phase, extract what it provides and what it should consume. From SUMMARYs, extract:
Build provides/consumes map:

2. Verify Export Usage

For each phase’s exports, verify they’re imported and used. Check imports:

3. Verify API Coverage

Check that API routes have consumers. Find all API routes:
Check each route has consumers:

4. Verify Auth Protection

Check that routes requiring auth actually check auth. Find protected route indicators:
Check auth usage in protected areas:

5. Verify E2E Flows

Derive flows from milestone goals and trace through codebase.

6. Compile Integration Report

Structure findings for milestone auditor. Wiring status:
Flow status:

What It Produces

Integration Report

Critical Rules

Check connections, not existence. Files existing is phase-level. Files connecting is integration-level.Trace full paths. Component → API → DB → Response → Display. Break at any point = broken flow.Check both directions. Export exists AND import exists AND import is used AND used correctly.Be specific about breaks. “Dashboard doesn’t work” is useless. “Dashboard.tsx line 45 fetches /api/users but doesn’t await response” is actionable.Return structured data. The milestone auditor aggregates your findings. Use consistent format.

Verifier

Verifies individual phases (integration checker verifies between phases)

Executor

Creates the integrations that checker verifies