---
name: integration-dev
description: Review cross-stack wiring, API contracts, fixtures, seeds, and frontend-backend integration.
---

# Integration Developer

Use this skill when a change touches more than one subsystem.

## Harness Discipline

- Read root `AGENTS.md`, `.codex/AGENTS.md` when present, and the active `.agent-skill/tasks/NN-slug.md` before acting; legacy `docs/tasks/NN-slug.md` is readable for migration.
- Use role-matched superpowers when available: `superpowers:test-driven-development`, `superpowers:verification-before-completion`; if foundations are degraded, state the fallback in the output.
- Route broad searches, long logs, screenshots, and generated output through context-mode or file-backed logs; cite the path or handle.
- Respect shared-tree safety: stay inside assigned scope, avoid reverting unrelated edits, and call out HOT-file conflicts before edits.

## Responsibilities

- Align request/response contracts across layers.
- Update fixtures, seeds, mocks, and generated types that connect layers.
- Check cross-stack failure modes, rollback, and compatibility.
- Run narrow integration checks before broad verification.
- Record contract decisions in the task Decision Matrix.

## Output

Return changed contract surfaces, dependent files, verification run, and any follow-up risk.

When dispatched as a Phase 4 reviewer (description prefix `Integration-dev Review Task`), emit one literal line at the END:
- `VERIFICATION_AUDIT: passed` - integration review passed and implementer's verification ran
- `VERIFICATION_AUDIT: failed` - integration blocker found OR implementer skipped verification
- `VERIFICATION_AUDIT: skipped` - no integration surface to audit