Research: event-driven-architect
Cached research evidence for event-driven-architect (not authority).
Quick Answer
Section titled “Quick Answer”Problem: Design event-driven systems: contracts, topics, consumers, retries, idempotency, and sagas. Use for asynchronous workflows. NOT for CRUD APIs or ETL pipelines.
Stack / assumptions: on-demand references; eval fixtures
Comparable alternative: A general-purpose agent instruction without a scoped skill contract
Repo summary:
Design asynchronous systems built around durable events, explicit contracts, and operationally safe consumers.
> Grounded in repository skills/event-driven-architect/SKILL.md; treat as evidence, not authority.