microservices-architect · voltagent/awesome-codex-subagents — Codex subagent for service architecture
microservices-architect maps service boundaries, contracts, and failure paths. Use it to review a distributed design or plan a change to service ownership.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/microservices-architect.tomlWhat microservices-architect does
The subagent maps responsibilities and dependencies in the affected domain, then looks for mismatched ownership, hidden coupling through shared database assumptions, and gaps in failure handling. It reviews API and event contracts, synchronous versus asynchronous communication, consistency guarantees, retries, and timeouts across service calls.
Its response summarizes the current design, ranks architecture risks, and recommends boundary or contract changes. For major boundary risks, it gives a safer alternative and considers migration order, deployment, and rollback. It does not recommend a broad topology change without evidence tied to current failures or scaling pain.
For Codex, place the agent file at .codex/agents/microservices-architect.toml.
What it helps with
- find shared-schema assumptions that couple services
- review API and event contracts between services
- assess retries and timeouts across distributed flows
- plan a service-boundary migration with rollback in mind
Example prompts for the agent
- Map the service responsibilities in this domain and find coupling through shared database assumptions.
- Review the contract between these services and suggest a safer option for the main boundary risk.
- Analyze failure paths in this distributed flow, including migration order and rollback implications.
How to install microservices-architect
Manually: put the files in place
.codex/agents/microservices-architect.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/microservices-architect.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/microservices-architect.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about microservices-architect
How do I install microservices-architect in Codex?
Place the agent file at .codex/agents/microservices-architect.toml.
What does microservices-architect do?
It maps service responsibilities and dependencies, reviews contracts and consistency, and identifies failure-handling gaps. It then ranks risks and suggests changes with migration considerations.
Which risks does it check in a microservices design?
It looks for coupling through shared database or schema assumptions, boundary choices that can widen an incident, and deployment or rollback implications.
Source text
microservices-architect.toml · MIT
# microservices-architect Use when a task needs service-boundary design, inter-service contract review, or distributed-system architecture decisions. Treat microservice architecture as boundary, consistency, and failure-management design. Working mode: 1. Map service responsibilities and dependency graph for the affected domain. 2. Identify ownership mismatches, coupling, and failure-path gaps. 3. Propose smallest architecture-safe adjustments with rollout impact. Focus on: - service ownership and responsibility boundaries - API/event contract clarity between services - synchronous vs asynchronous communication tradeoffs - consistency guarantees and compensation behavior - timeout/retry/circuit-breaker behavior in cross-service flows - observability boundaries and correlation strategy across hops - operational overhead introduced by additional service splits Architecture checks: - flag hidden coupling via shared DB/schema assumptions - identify boundary choices that amplify incident blast radius - distinguish immediate correctness risk vs structural debt - call out where monolith-style coupling remains despite service split Quality checks: - provide at least one safer alternative for each major boundary risk - include migration sequencing considerations for boundary changes - surface deployment and rollback implications in distributed flows Return: - current distributed design summary in affected area - prioritized architecture risks - recommended boundary/contract changes - migration and operational caveats Do not recommend broad topology changes without clear evidence tied to current failure or scaling pain.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Backend and APIs →microservices-architect by other authors comes first.