Event Driven Architecture
Designs event-driven systems with asynchronous flows, brokers, producers, consumers and contracts. Use when architecting asynchronous, decoupled, or event-first systems.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-event-driven-architecture ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Event-Driven Architecture
When to use
Use when designing asynchronous integration or event-first systems.
Objective
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Procedure
- Identify triggers and outcomes.
- Separate events, commands and queries.
- Identify producers/consumers.
- Define topics/streams.
- Define schemas/contracts.
- Define ordering, partitioning, idempotency and replay.
- Define failure handling.
- Define observability.
Required outputs
- Event flow
- Producers/consumers
- Topic/stream design
- Contracts
- Ordering/idempotency/replay decisions
- Operational controls
Best-practice alignment
Apply event-driven best practice: business event semantics, producer/consumer ownership, schema contracts, compatibility, ordering, partitioning, idempotency, replay, retention, lineage, observability and operational SLOs.
Use open standards where they fit: CloudEvents for a common event envelope and metadata (id, source, type, time, dataschema), and AsyncAPI for application-level channel, operation and message contracts. CloudEvents and AsyncAPI are complementary (envelope vs interface).
Quality checks
- Events have business meaning.
- Ownership is clear.
- Duplicate/replay behaviour is handled.
- Observability exists.
Avoid
Do not use events to disguise tight coupling.
Decision aid
Choose event-driven architecture when producers and consumers can evolve independently, consumers need replay, or business facts must be observed by multiple domains. Prefer request/response when the caller needs an immediate answer and no other consumer benefits. For each event, record owner, contract, idempotency key, ordering assumption, retry policy and observable failure path.
References
Verification
- [ ] Required artefacts produced and linked to scope.
- [ ] Decisions, assumptions and risks stated explicitly.
- [ ] Quality checks or validation performed.
- [ ] Files changed reported with traceability preserved.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mmccalla
- Source: mmccalla/coding-agent-skill-library
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.