Event Storming
Apply Alberto Brandolini's Event Storming — a collaborative modeling technique using domain events on sticky notes to discover business processes, identify bounded contexts, and design software collaboratively. Covers Big Picture, Process Modeling, and Software Design levels, the color-coded sticky-note grammar, the workshop flow, and how Event Storming pairs with DDD. Use when starting a new project, exploring a complex domain, finding bounded-context seams, designing aggregates, or surfacing hidden assumptions across business and tech.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill event-storminggit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/event-storming ~/.claude/skills/event-stormingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Event Storming (Alberto Brandolini) Apply this skill when starting a new system, exploring an unfamiliar domain, finding bounded-context seams, designing aggregates, onboarding a team into a complex domain, or surfacing tacit knowledge that lives only in people's heads. Event Storming is a workshop format — collaborative, visual, fast — that produces a shared model from a roomful of stakeholders in hours rather than weeks. ## Core Philosophy **Domain events are the unit of discovery.** Not entities, not data models, not class diagrams. Events — past-tense facts about what happened — anchor every business process and reveal where complexity actually lives. **Knowledge lives in many heads, not one.** The domain expert knows the rules, the developer knows the constraints, the salesperson knows the edge cases, the support engineer knows the failures. Event Storming brings them all to one wall and lets the model emerge from their collective drawing. **Big sheets of paper beat slide decks.** A 10-meter roll of paper gives space for the model to sprawl and reshape. Sticky notes encode information cheaply and move freely. The medium is part of the method. **Find the chaos before resolving it.** The first half of a workshop is deliberately chaotic — everyone adds events without coordination. The chaos surfaces disagreements, gaps, and edge cases that would never appear in a tidy diagram drawn by one person. --- ## The Three Levels
Details
- Skill name
event-storming- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/event-storming/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Event Storming skill do?
Apply Alberto Brandolini's Event Storming — a collaborative modeling technique using domain events on sticky notes to discover business processes, identify bounded contexts, and design software collaboratively. Covers Big Picture, Process Modeling, and Software Design levels, the color-coded sticky-note grammar, the workshop flow, and how Event Storming pairs with DDD. Use when starting a new project, exploring a complex domain, finding bounded-context seams, designing aggregates, or surfacing hidden assumptions across business and tech.
How do I install the Event Storming skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Event Storming popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Flow Efficiency
5vnovakovits/claude-skills
Apply Niklas Modig & Pär Åhlström's flow-efficiency framework from "This is Lean — Resolving the Efficiency Paradox" (2012). Covers the central paradox (resource efficiency vs flow efficiency), the efficiency matrix, Kingman's formula and why high utilization destroys flow, the three laws of process dynamics (Little's Law, the law of bottlenecks, the law of variation), the "variation × utilization" killer combination, lean as an operational strategy not a tool, and the diagnostic vocabulary for explaining why "keeping everyone busy" actively harms delivery. Use when a team is busy but not ship
Domain Driven Design
5vnovakovits/claude-skills
Apply Domain-Driven Design (DDD) by Eric Evans and Vaughn Vernon when modeling complex business domains, designing aggregates, structuring bounded contexts, choosing between entities and value objects, or aligning code with domain language. Covers strategic design (ubiquitous language, bounded contexts, context mapping), tactical building blocks (entities, value objects, aggregates, domain events, services, repositories, factories), supple design, and refactoring toward deeper insight.
Fractal Architecture
5vnovakovits/claude-skills
Apply heuristics from Mark Seemann's "Code That Fits in Your Head" (2021) — fractal architecture, working-memory limits, cyclomatic complexity ceilings, vertical slices, encapsulation through invariants, functional core / imperative shell, checklists, and sustainable software engineering. Use when designing, decomposing, sizing methods/classes, deciding what fits in working memory, or evaluating whether code is sustainable over the long term.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.