Event Driven Architecture Planner
Design event-driven systems with domain events, ownership, schemas, ordering, retries, idempotency, consistency, and observability.
Event Driven Architecture Planner is a free AI skill for code improvement. Design event-driven systems with domain events, ownership, schemas, ordering, retries, idempotency, consistency, and observability. It works with Claude, ChatGPT, Cursor and is ready to use out of the box.
About this skill
Event Driven Architecture Planner converts tightly coupled workflows into a clear event-driven architecture. It defines business events, producers, consumers, schemas, ownership, ordering, delivery guarantees, idempotency, retries, dead-letter handling, eventual consistency, replay, monitoring, and migration steps.
What it does
The skill analyzes business workflows, transaction boundaries, services, data ownership, and failure modes; determines which interactions should be events, commands, or synchronous calls; defines contracts and reliability behavior; and produces a phased implementation plan with operational controls.
What is included
- Event and command map
- Producer and consumer ownership
- Event schema definitions
- Ordering and delivery rules
- Idempotency and retry design
- Consistency and compensation model
- Replay and recovery strategy
- Migration and observability plan
How to use it
1. Download the event-driven-architecture-planner-SKILL.md file 2. Upload it to your engineering workspace 3. Provide current workflows, services, databases, and integration pain points 4. Add scale, ordering, latency, and consistency requirements 5. Use the plan to implement the architecture incrementally
Examples
Design an event-driven architecture for an e-commerce platform handling orders, payments, inventory, shipping, refunds, and customer notifications.
A complete event map with producers, consumers, schemas, ownership, delivery guarantees, idempotency, sagas, retries, dead letters, replay, metrics, and migration phases.
FAQ
What is this skill for?
Does it recommend events for every interaction?
Can it design sagas?
How does it handle duplicate events?
Does it include schema evolution?
How is this different from drawing a message-flow diagram?
Related Skills
Caching and Performance Architecture Planner
Design caching strategies with keys, invalidation, consistency, TTLs, stampede protection, observability, and performance tests.
Monorepo Architecture and Build Planner
Design monorepo structure, package boundaries, build graphs, ownership, caching, CI, releases, and migration strategy.
Error Taxonomy and Resilience Pattern Designer
Design consistent error categories, propagation, retries, user messages, observability, recovery, and resilience patterns.