Process Level Event Storming

Apply Alberto Brandolini's Process Modeling level of Event Storming — modeling ONE business process in full sticky-note grammar (read model → actor → command → aggregate/external system → event → policy → …) on a timeline, with hot spots as first-class output. Covers the picture-that-explains-everything loop, grammar rules, completeness walks (backwards walk, orphan checks, missing failure paths), swimlane/frame layout for remote boards (Miro/Mural/FigJam), and mapping the model onto process managers, sagas, and workflow code. Use when designing or documenting a single process end-to-end, mode

5 stars 2 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill process-level-event-storming
Manual install
git 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/process-level-event-storming ~/.claude/skills/process-level-event-storming

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Process-Level Event Storming (Alberto Brandolini)

Apply this skill when one specific business process needs to be modeled in detail — a new feature's flow, an existing workflow you're changing, a cross-service saga you're reviewing. It assumes the scope is already known (from a Big Picture session or simply from the ticket); for whole-domain discovery, use the companion `event-storming` skill.

The output is a **process model**: a left-to-right timeline in the full sticky-note grammar, precise enough to walk into code, with every unknown marked as a hot spot rather than smoothed over.

---

## The Picture That Explains Everything

Brandolini's process-level grammar is one repeating loop:

```
(green)        (small yellow)   (blue)        (large yellow / pink)   (orange)       (lilac)
Read Model  →  Actor         →  Command    →  Aggregate or         →  Domain      →  Policy  →  next Command …
"what they     "who decides"    "the intent"   External System         Event          "whenever X,
 looked at"                                    "what decides"          "the fact"      then Y"
```

Every complete process is this loop unrolled along a timeline. When a step is missing, that's not a simplification — it's a gap in understanding. The loop closes when a policy (or an actor reading a read model) issues no further command: the process is complete.

## The Grammar

| Sticky | Color & shape | Form | Rule |
|---|---|---|---|
Read the full skill on GitHub

Details

Skill name
process-level-event-storming
Path
plugins/engineering-practices/skills/process-level-event-storming/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Process Level Event Storming skill do?

Apply Alberto Brandolini's Process Modeling level of Event Storming — modeling ONE business process in full sticky-note grammar (read model → actor → command → aggregate/external system → event → policy → …) on a timeline, with hot spots as first-class output. Covers the picture-that-explains-everything loop, grammar rules, completeness walks (backwards walk, orphan checks, missing failure paths), swimlane/frame layout for remote boards (Miro/Mural/FigJam), and mapping the model onto process managers, sagas, and workflow code. Use when designing or documenting a single process end-to-end, mode

How do I install the Process Level 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 Process Level Event Storming popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/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

Frontend & Design

Agent Retro

5

vnovakovits/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

AI, LLMs & Agents

API Design

5

vnovakovits/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.

Software Development

Project Orchestrator

8

Freddy-CHEN-ux/00_claude_skills

Orchestrate multi-phase project implementation using background Claude agents for isolated development, review, and integration.

AI, LLMs & Agents

Parallel Agent Workflow

5

bolasblack/claude-skills

Coordinate multiple agents working in parallel using git worktrees to avoid file conflicts. Use when needing concurrent agents to modify different files/components with worktree isolation, or when asked to use worktrees for parallel agent work.

AI, LLMs & Agents

Remote Code Agents

8

Freddy-CHEN-ux/00_claude_skills

Delegate tasks to remote Claude Code agent containers for parallel execution, long-running analysis, or resource-intensive operations.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.