All skills
event-driven-architecture
FoundationJIT onlyanalysis-agent/task-agent: use when event flow, ordering, idempotency, replay, backpressure, or eventual consistency changes; skip when no event-driven decision is needed.
- Group
- Architecture & design
- Supported roles
- MainAnalysisTaskReview
- Source
- SKILL.md
Use when
Trigger signals that make this skill the right owner
- design asynchronous event flow ordering idempotency replay and eventual consistency
Do not use when
Anti-triggers — as binding as the triggers above
- no task-local event driven architecture decision is required
Required inputs
What must be supplied before this skill can decide anything
- current task contract
- selected primary Professional Skill
- task-local trigger evidence
Output contract
What this skill owes the next role
- event architecture decision with event meaning, topology, consistency boundary, delivery identity and ordering, replay and backpressure, compatibility, failure evidence, and residual owners
Escalation signals
When this skill must hand the decision back
- Event systems fail through duplicate messages ordering gaps and invisible lag
Loaded by
This skill never owns a task. These professionals may pull it in as Layer 3.
Targeted references
Each reference carries its own load condition. None of them enter context by default.
| Reference | Load when | Do not load when | Required by |
|---|---|---|---|
| benchmarks-and-patterns.mdbenchmark-pattern | Delivery, ordering, workflow, replay, or backpressure mechanisms compete. | No event topology or consistency decision changes. | AnalysisTask |
| checklist.mddecision-checklist | Architecture changes producers, consumers, DLQs, schemas, or irreversible effects. | No asynchronous event flow is affected. | AnalysisTask |
| topology-evidence-freshness.mdevidence-pattern | Topology approval depends on fresh contracts, drills, or lag evidence. | No producer-consumer completeness claim awaits approval. | AnalysisTask |