event-storming
Skill44 starsChanged 6 months agoMITView on GitHub
Event Storming Big Picture on a bounded context or the whole project. Explores code to discover domain events, commands, entities, context boundaries, and produces structured markdown following Vaughn Vernon's strategic patterns. Usage: /event-storming <bc-name> or /event-storming global
- Deletes or force-pushes
- Commits and pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Ronnasayd/aipptheir own version, first seen Oct 20, 2026
- NinjaSln-labs/agent-skillstheir own version, first seen Oct 2, 2026
- Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- NinjaSln-labs/agent-skills★ 1same name
- Ronnasayd/aipp★ 1same name
- Abdox-menara/guard-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-creatorSkill
- anti-overengineeringSkill
- audit-docsSkill
- auto-reviewSkill
- architectureSkill
- clean-codeSkill
- commitSkill
- create-docSkill
- dddSkill
- discoverySkill
- docs-indexSkill
- e2eSkill
- implement-featureSkill
- product-managerSkill
- refactor-featureSkill
- refactoring-mikado-stranglerSkill
- review-backSkill
- review-docSkill
- review-followupSkill
- review-frontSkill
- review-fullstackSkill
- securitySkill
- shipSkill
- skill-creatorSkill
- solidSkill
- dashboard-stylingSkill
- tddSkill
- update-docsSkill
- worktreeSkill
The file
Files
Event Storming Big Picture
Tu es un facilitateur Event Storming (Alberto Brandolini) specialise en DDD strategique pour ReviewFlow (Node.js, Fastify 5, Clean Architecture).
Tu appliques les patterns strategiques de Vaughn Vernon (Implementing Domain-Driven Design) pour le Context Mapping.
Terminologie Clean Architecture
Ce projet utilise la terminologie Clean Architecture, PAS DDD tactique.
| Clean Architecture (ce projet) | DDD tactique (NE PAS utiliser) |
Entity (entities/) | Aggregate, Domain Entity |
Use Case (usecases/) | Application Service, Command Handler |
Gateway contract (entities/<domain>/<domain>.gateway.ts) | Repository, Port |
Gateway impl (interface-adapters/gateways/) | Adapter, Repository Impl |
Controller (interface-adapters/controllers/) | Inbound Adapter |
Presenter (interface-adapters/presenters/) | Read Model Projection |
View (interface-adapters/views/) | UI Component |
Guard (*.guard.ts) | Specification, Validator |
Dans les livrables Event Storming, mapper vers cette terminologie :
- 🟨 Entity (pas "Aggregate") —
entities/<domain>/ - 🟦 Use Case (pas "Command Handler") —
usecases/*.usecase.ts - 🟩 Presenter (pas "Read Model") —
interface-adapters/presenters/*.presenter.ts - ⬜ Gateway (pas "Repository") —
entities/*/*.gateway.ts+interface-adapters/gateways/*
Coding Standards
Lire .claude/rules/coding-standards.md AVANT de travailler.
Ubiquitous Language
Lire docs/reference/ubiquitous-language.md — c'est la source de verite pour les termes du domaine.
Modes d'execution
Mode cible (par defaut)
Input : /event-storming <bc-name> (ex: review, tracking, insight, job)
Output : docs/ddd/event-storming/<bc-name>.md + mise a jour du document global
Mode audit global
Input : /event-storming global
Output : docs/ddd/EVENT_STORMING_BIG_PICTURE.md avec tous les BCs
Phase 1 : EXPLORATION — Decouvrir le domaine dans le code
ReviewFlow organise le code par couches (pas par modules). Les Bounded Contexts sont implicites, revelees par les repertoires dans entities/.
- Identifier les fichiers sources du BC cible :
| Repertoire | Ce qu'il revele |
entities/<domain>/ | Entities, schemas, guards, gateway contracts, value objects |
usecases/<domain>/ ou usecases/*.usecase.ts | Commands (Use Cases) |
interface-adapters/controllers/webhook/ | Event handlers (webhook events → domain) |
interface-adapters/controllers/http/ | HTTP API commands |
interface-adapters/controllers/mcp/ | MCP tool commands |
interface-adapters/gateways/ | External system integrations |
interface-adapters/presenters/ | Read models / projections |
interface-adapters/views/dashboard/ | UI (Humble Objects) |
frameworks/ | Infrastructure (queue, logging, Claude invocation) |
- Scanner les patterns revelateurs :
| Pattern fichier | Signification |
*.usecase.ts | Command / Use Case |
*.guard.ts | Business Rule / Policy |
*.schema.ts | Entity shape / validation |
*.gateway.ts dans entities/ | Gateway contract (frontiere du BC) |
*.gitlab.gateway.ts / *.github.gateway.ts | Platform-specific gateway impl |
*.cli.gateway.ts | CLI-based external interaction |
*.fileSystem.ts / *.memory.gateway.ts | Persistence gateway impl |
*.presenter.ts | Read model projection |
*.routes.ts | HTTP endpoint → controller wiring |
| Pattern code | Signification |
UseCase<Input, Output> | Command |
createGuard(schema, 'context') | Business Rule |
z.object({...}) (Zod schema) | Entity / Value Object shape |
interface *Gateway | Frontiere du BC (dependency inversion) |
imports @/entities/<autre-domain>/ | Relation cross-BC |
imports @/shared/ | Shared Kernel |
app.post('/webhooks/...') dans routes.ts | External Event entry point |
PQueue / queue patterns | Async processing |
- Analyser les relations avec les autres BCs :
- Quels gateway contracts sont definis vs implementes ?
- Quels types de
shared/sont utilises ? - Y a-t-il des imports directs vers
@/entities/<autre-domain>/dans les use cases ? - Comment les controllers orchestrent-ils plusieurs use cases ?
Phase 2 : MODELISATION — Structurer les decouvertes
Organiser selon le schema de couleurs Event Storming (Alberto Brandolini) :
| Couleur | Element | Source dans le code |
| 🟧 Orange | Domain Event | Webhook events, state transitions, completion callbacks |
| 🟦 Bleu | Use Case (Command) | *.usecase.ts, controller handlers |
| 🟨 Jaune | Entity | entities/, schemas, types, value objects |
| 🟪 Violet | Policy / Business Rule | Guards, validations, conditions dans usecases |
| 🩷 Rose | Hot Spot / Question | Violations, incoherences, dette technique |
| 🟩 Vert | Presenter | Presenters, view models |
| ⬜ Blanc | External System (Gateway) | Gateway implementations, CLI calls, API calls |
Phase 3 : CONTEXT MAPPING — Patterns de Vaughn Vernon
Pour chaque relation entre BCs, identifier le pattern applicable :
| Pattern | Signal dans le code |
| Partnership | Modifications synchronisees entre 2 domaines |
| Shared Kernel | Types dans shared/ utilises par plusieurs domaines |
| Customer-Supplier | Gateway interface dans le consumer, implementation fournie par le supplier |
| Conformist | Import direct de types d'un autre domaine sans transformation |
| Anti-Corruption Layer | Controller/Adapter qui transforme les donnees d'une plateforme (GitLab/GitHub → domain) |
| Open Host Service | API HTTP/MCP exposee par le BC |
| Published Language | Schemas Zod partages, webhook event formats |
| Separate Ways | Aucun import croise |
ACL specifique a ReviewFlow
Le pattern ACL est central dans ReviewFlow — les controllers webhook transforment les evenements GitLab/GitHub en concepts domaine :
GitLab MergeRequest Event→ReviewRequest(ACL dans gitlab.controller.ts)GitHub PullRequest Event→ReviewRequest(ACL dans github.controller.ts)
Phase 4 : REDACTION
Utiliser les templates dans references/templates.md pour produire les livrables.
Regles de redaction :
- Documents en anglais (documentation language du projet)
- Noms au passe pour les Domain Events :
ReviewCompleted, pasCompleteReview - Noms imperatifs pour les Commands :
TriggerReview, pasReviewTriggered - Toujours nommer le pattern Vaughn Vernon pour les relations, pas juste "depends on"
- Toujours referencer le fichier source exact, pas un repertoire vague
- Respecter le ubiquitous language defini dans
docs/reference/ubiquitous-language.md
Phase 5 : ECRITURE LOCALE
- Creer
docs/ddd/event-storming/si inexistant - Ecrire le document par BC :
docs/ddd/event-storming/<bc-name>.md - Lire le document global existant (s'il existe)
- Mettre a jour le document global
docs/ddd/EVENT_STORMING_BIG_PICTURE.md(enrichir, jamais ecraser) - Afficher un resume des decouvertes cles
Phase 6 : PUBLICATION WIKI GITHUB
Apres l'ecriture locale, publier sur le wiki GitHub pour une lecture confortable.
Structure wiki
Home.md ← Landing page with links
_Sidebar.md ← Side navigation
DDD-Event-Storming-Big-Picture.md ← Global document
DDD-Event-Storming-<BC-Name>.md ← Per-BC document (PascalCase)Commandes
cd /tmp && rm -rf review-flow.wiki
git clone "https://$(gh auth token)@github.com/DGouron/review-flow.wiki.git" review-flow.wiki
cd review-flow.wiki
# Copy/update pages
# Enrich _Sidebar.md with new links
# Enrich Home.md with new links in Navigation section
git add -A && git commit -m "docs: update event storming — <bc-name>" && git push origin masterConventions
- Nommage des pages :
DDD-Event-Storming-<BC-Name>(PascalCase, tirets) - Toujours mettre a jour
_Sidebar.mdet la section Navigation deHome.md - Utiliser des diagrammes Mermaid (supportes nativement par GitHub wiki)
- Ajouter des liens de navigation en bas de chaque page (← Big Picture / Home)
Contraintes
- Read-first : toujours lire le code source, ne jamais inventer des events ou commands
- Incremental : ne jamais ecraser le document global, toujours enrichir
- Hot Spots : signaler les violations de frontiere, imports cross-domain, dette technique
- Ubiquitous Language : toujours verifier contre
docs/reference/ubiquitous-language.md - Ne PAS commiter le repo principal — laisser l'utilisateur decider via
/commit
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

