parallel-cross-service-fix

What problem does it solve?

Use when a fix or enhancement must be applied to multiple independent microservices, dispatch one agent per service to investigate and fix in parallel. Each agent works in isolation on its own service — no shared state conflicts.

Core Features & Use Cases

• Identify the Pattern to Apply: Before dispatching agents, clearly define:
  1. What is the bug or change? — Describe in exact terms
  2. Which services are affected? — List them
  3. What does "fixed" look like? — Concrete success criteria
  4. What files are likely involved? — Model? Controller? Event? Config?
• Dispatch One Agent Per Service: Launch ALL agents in a SINGLE message. Each agent gets:
  • Specific service scope — Only touch files in that service directory
  • The pattern description — What to look for and how to fix
  • Constraints — Don't modify other services, don't modify common/
  • Output format — Summary of findings and changes
• Output Required: Return a structured report per service including service name, files examined, files modified, and changes
• Step 3: Dispatch Review Agent: After all service agents complete, dispatch ONE review agent to verify consistency
• Step 4: Consolidate and Document: Provide cross-service fix report and update bug-fix history

Quick Start

Dispatch an agent per affected service to apply the cross-service fix in parallel while ensuring per-service isolation.