integration-architect

Validates cross-repo interface contracts by comparing branch diffs against planned integration specifications.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill integration-architect-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-architect
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/integration-architect
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill integration-architect-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple developers or agents implement a feature in parallel across separate repositories, interface drift (mismatched field names, changed endpoints, type conflicts) often goes undetected until merge time. This Skill inspects the actual diffs from each feature branch and verifies that producers and consumers honor the contracts defined in the architecture plan before anything is merged. ## Core Features & Use Cases - Contract Extraction from Diffs: Reads git diffs per repo and extracts actual HTTP routes, data model fields, shared library APIs, and message schemas. - Producer/Consumer Validation: Compares each planned contract against real implementations, detecting field name mismatches, type drift, endpoint changes, and nullability conflicts. - Structured Integration Reports: Writes a PASS/WARN/FAIL report to .workflow/reports/ and, on failure, generates rework task files in .workflow/tasks/ for the Coordinator to dispatch. - Use Case: After three coder agents finish a feature spanning a backend API, a mobile app, and a shared library, run this Skill to confirm the mobile app consumes exactly the fields the backend produces before merging all branches. ## Quick Start Ask the agent to run an integration check for the current feature by reading the plan in .workflow/plans and comparing all completed task branch diffs against the defined interface contracts.

Frequently Asked Questions about integration-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate API contracts between microservices before merging?▼

Run an integration check that extracts actual interfaces from each branch's git diff and compares them against the planned contracts. The Skill checks HTTP routes, request/response fields, types, and status codes, then reports PASS, WARN, or FAIL per contract.

How to detect breaking changes across multiple git repositories?▼

Compare producer and consumer implementations by diffing each feature branch against the default branch. The Skill flags field name mismatches, type changes, removed fields, endpoint drift, and nullability conflicts between repos.

What happens when the integration check finds a contract violation?▼

On FAIL findings, the Skill writes a detailed integration report and creates new coder task files in .workflow/tasks/ describing each violation and its required fix. The Coordinator then dispatches rework, and the integration check re-runs after fixes complete.

Does the integration check modify feature branches or application code?▼

No. The Skill is strictly read-only with respect to feature branches and application code. It only reads diffs, writes report files, and creates rework task files; it never edits implementations.

What are the prerequisites for running a cross-repo integration check?▼

All coder tasks for the feature must have status done, and the workspace must contain agent.yaml, a plan file in .workflow/plans/, and task files in .workflow/tasks/. If any task is incomplete, the check stops and reports pending work.