Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Event Modeling · nwave-ai | DecimalAI

codingby nwave-ai

Event Modeling

nwave-ai/nw-ddd-event-modeling

Source nwave-ai/nwave ↗License MIT

Event Modeling facilitation technique — brainstorm events, identify commands and views, define aggregate boundaries, write Given-When-Then specifications

SkillScore78Maintained

On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.

Coding pack

Last verified 8/16/2026

What it changes

Passed 18 of 23 test cases with the skill, and 13 of 23 without it.

Without skill57%

With skill78%

Checks it passed that the model alone missed

Positions UI wireframe screens at the top row.
Classifies automated system policies as Yellow.
Places command stickies above the timeline event stickies.

and 8 more in the full report

6 fixed12 passed either way4 still failing1 broke

Pass-rate lift: +22 pp
Tokens: +67%
Agent turns: 0%
Response time: -28%

Model gemini-3.6-flashMeasured 8/16/2026v118 of 23 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/nwave-ai-nw-ddd-event-modeling/SKILL.md https://app.decimal.ai/s/nwave-ai-nw-ddd-event-modeling/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add nwave-ai-nw-ddd-event-modeling, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/nwave-ai-nw-ddd-event-modeling/ and pins it in .decimal/skills.lock

decimalai skills add nwave-ai-nw-ddd-event-modeling

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/nwave-ai-nw-ddd-event-modeling/SKILL.md https://app.decimal.ai/s/nwave-ai-nw-ddd-event-modeling/SKILL.md

Raw file: /s/nwave-ai-nw-ddd-event-modeling/SKILL.md ↗ · machine-readable summary at /s/nwave-ai-nw-ddd-event-modeling.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 6

Prompt

In Phase 2 of modeling a subscription management flow, we are adding commands and read models. Which side of the timeline event stickies should commands and read models be placed?

What was checked, without and with the skill
Checked	Without skill	With skill
Places command stickies above the timeline event stickies.	Missed	Passed
Places read model stickies below the timeline event stickies.	Missed	Passed

case-08 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md152 linessingle file

Event Modeling

Collaborative visual design technique created by Adam Dymitruk. The Event Model IS the specification -- it replaces traditional requirements documents with a single, living visual artifact.

Key Properties

Collaborative: Everyone participates (devs, business, UX)
Visual: Colored elements on a timeline (physical or digital board)
Timeline-based: Events arranged chronologically, left to right
Spec-generating: Model directly produces testable Given/When/Then specifications
Technology-agnostic: Describes WHAT happens, not HOW it's implemented

The Color System

Color	Element	Description	Example
Orange	Event	Something that happened (past tense)	OrderPlaced, PaymentReceived
Blue	Command	User intent/action (imperative)	PlaceOrder, ProcessPayment
Green	Read Model/View	Data displayed to user	Order Summary, Shipping Dashboard
White	Screen/UI	User interface wireframe	Order Form, Checkout Page
Yellow	Automation/Policy	System reaction (saga/process manager)	"When PaymentReceived, then ConfirmOrder"
Red	External System	Integration point	Payment Gateway, Email Service

Four Phases

Phase 1: Event Brainstorming (10-20 min)

Discover all meaningful things that happen in the system.

Process: Everyone writes events on orange stickies (past tense, domain language) | Place on timeline (left = earlier, right = later) | No filtering -- capture everything | Group related events vertically (these form swimlanes/slices)

Facilitation tips:

Start with the happy path -- what happens when everything goes right?
Then add error/exception events
Ask: "What happens before this? What happens after?"
Business people identify events developers miss
Don't worry about order precision -- rough chronological is fine

Example timeline:

Track record

Benchmark

18 / 23

test cases passed, vs 13 / 23 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

nwave-ai / nwave

nWave/skills/nw-ddd-event-modeling/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Event Modeling

Key Properties

The Color System

Four Phases

Phase 1: Event Brainstorming (10-20 min)

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills