What problem does it solve? Wiring a new feature, service, worker, or dependency into a larger system often breaks things at the seams: unenforced contracts, unbounded retries, hidden shared resources, and edges with no owner. This Skill provides a structured checklist for proving that a component integrates safely with the whole system, in both directions. ## Core Features & Use Cases - Whole-System Mapping: Surfaces shared substrates, boot cycles, cold-start risks, and existing control loops before wiring anything in. - Boundary Contract Enforcement: Pins producer/consumer contracts with schemas and contract tests, tolerating additive changes while rejecting invariant violations. - Bidirectional Blast Radius Analysis: Bounds what the system can do to your part (timeouts, breakers, fallbacks) and what your part can do to the system (load, fan-out, quotas). - Use Case: When adding a new worker that consumes from a shared queue owned by another team, use this Skill to define the contract test, cap retries with jitter and deadlines, plan a dark launch, and assign an owner with a sunset date for the new edge. ## Quick Start Ask the AI to run a structural integration review on the new service or dependency you are wiring into the system, covering contracts, blast radius, and rollout proof.
