I built a Claude Code plugin to handle multi-service coordination

You're deep into a feature. Claude Code is handling changes across three services. You're watching it work, and it looks good — until you realize session A renamed a field in auth-service two hours ago, and session B has been building order-service against the old shape ever since. Nothing failed loudly. It just drifted. This is the problem I kept hitting when using Claude Code on a multi-service project. Inside a single repo, it's genuinely impressive. But the moment a change needs to flow through interconnected services — API contracts, shared models, downstream consumers — the coordination falls apart. Not because Claude Code is bad, but because it was never designed for this. Each session has its own context. They don't talk to each other. There's no shared awareness of what changed where. The result: field names diverge quietly, contracts go stale, and downstream services code against schemas that no longer exist. You don't find out until something breaks in staging. The coordinat