Event Modeling
Discovers and models business events, commands, decisions and state changes. Use when event-storming, designing event timelines, or defining domain events.
Install
$ agentstack add skill-mmccalla-coding-agent-skill-library-event-modeling ✓ 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mmccalla-coding-agent-skill-library-event-modeling) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Event Modelling
When to use
Use when identifying event semantics before schema or topic design.
Objective
Produce a practical, concise, traceable architecture artefact that a coding agent can use to guide implementation or review.
Procedure
- Identify process/value stream.
- Map trigger-to-outcome timeline.
- Identify commands, events, decisions and read models.
- Name events in past tense.
- Define event meaning and payload concepts.
- Identify correlation/causation IDs.
- Validate language with business stakeholders.
Required outputs
- Event timeline
- Command/event list
- Event definitions
- Payload concepts
- Identifiers
- Open questions
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. After semantics are agreed, map payloads to CloudEvents envelopes and AsyncAPI (or schema-registry) contracts where interoperability matters.
Quality checks
- Events are past-tense facts.
- Commands are not modelled as events.
- Names match business language.
Avoid
Do not name events after database operations.
Decision aid
Start with sticky-note style discovery: commands in imperative form, events in past tense, decisions as policy points and read models as views. If a candidate event is named UpdateCustomer, challenge it until the business fact is clear, such as CustomerAddressChanged. Capture open questions where language is disputed.
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.