Design event-driven systems: contracts, topics, consumers, retries, idempotency, and sagas. Use for asynchronous workflows, reliability patterns, retry/replay design, DLQ handling. NOT for CRUD APIs or ETL pipelines.
Installs into .claude/skills of the current project.
Are you the author of Event Driven Architect?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/martineserios-event-driven-architect)
---
name: event-driven-architect
description: "Design event-driven systems: contracts, topics, consumers, retries, idempotency, and sagas. Use for asynchronous workflows, reliability patterns, retry/replay design, DLQ handling. NOT for CRUD APIs or ETL pipelines."
group: brana
keywords: [event-driven, async, events, sagas, idempotency, dlq, pub-sub, outbox, reliability, state-machine]
allowed-tools: [Read, Write, Edit, Glob, Grep, AskUserQuestion]
status: experimental
source: "github.com/wyattowalsh/agents/skills/event-driven-architect"
acquired: "2026-05-14"
quarantine: false
---
<!-- PROCEDURE_FILE: procedures/event-driven-architect.md -->
This skill's full procedure is in a separate file for startup performance (ADR-034).
Read and execute `system/procedures/event-driven-architect.md` from the plugin root directory.
If the path doesn't resolve, use Glob to find `**/procedures/event-driven-architect.md`.
