Microservice Designer

Microservice Designer — Microservice Architecture Design Pipeline

An agent team collaborates to perform domain analysis -> service design -> communication design -> observability design.

Execution Mode

Agent Team — 5 members communicate directly via SendMessage and cross-validate each other.

Agent Composition

Workflow

Phase 1: Preparation (Performed directly by Orchestrator)

1. Extract from user input:
   • Business Domain: What system/service is being designed
   • Current State (optional): Whether this is a monolith migration or a greenfield design
   • Scale/Constraints (optional): Expected traffic, team size, technology stack limitations
   • Existing Documentation (optional): ERD, architecture documents, API documentation, etc.
2. Create _workspace/ directory at the project root
3. Organize input and save to _workspace/00_input.md
4. If existing files are available, skip the corresponding Phase

Phase 2: Team Assembly and Execution

Tasks 3a (communication) and 3b (observability) can be executed in parallel.

Inter-team Communication Flow:

• analyst completes -> delivers bounded contexts and aggregates to architect; delivers domain events to comm-designer
• architect completes -> delivers service catalog and API contracts to comm-designer; delivers service list and dependencies to obs-engineer
• comm-designer completes -> delivers communication matrix and Saga flows to obs-engineer
• reviewer cross-validates all deliverables. When RED Must Fix items are found, requests fixes from the relevant agent -> rework -> re-verification (up to 2 times)

Phase 3: Integration and Final Deliverables

1. Check all files in _workspace/
2. Verify that all RED Must Fix items from the review report have been addressed
3. Report the final summary to the user

Modes by Task Scale

Data Transfer Protocol

Error Handling

Test Scenarios

Normal Flow

Prompt: "Design an e-commerce platform with microservice architecture. Order, payment, shipping, inventory, and user management are the core features." Expected Result:

• Domain: 5 bounded contexts, context map, event storming results
• Service: 5-7 service catalog, API contracts, data ownership mapping
• Communication: Order-Payment-Shipping Saga, event bus topic design, circuit breaker configuration
• Observability: SLI/SLO definitions, distributed tracing design, alerting system
• Review: Full consistency verification across all items, distributed system anti-pattern checks

Existing File Utilization Flow

Prompt: "I want to migrate a Django monolith to MSA. I have ERD and API documentation." + file attachments Expected Result:

• Reverse-extract bounded contexts from the existing ERD
• Include Strangler Fig pattern-based gradual migration roadmap
• Include existing API backward compatibility maintenance strategy

Error Flow

Prompt: "Build a chat app with microservices" Expected Result:

• Distinguish between "design" and "implementation," performing only design
• Include communication design specialized for real-time communication (WebSocket/SSE)
• Inform that implementation is outside the scope of this skill

Agent Extension Skills