storm-prep

Analyze codebases to discover domain events and output structured YAML.

14|6|Updated Feb 3, 2026

Search Tags:#ddd #code exploration #domain events #event storming #yaml generation #assumption surfacing

Ready to run

npx skills add https://github.com/tyevans/tackline --skill storm-prep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: storm-prep
Source: https://github.com/tyevans/tackline/tree/main/skills/workflows/storm-prep
Command: npx skills add https://github.com/tyevans/tackline --skill storm-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the initial discovery of domain events and boundary assumptions for Event Storming sessions, preparing structured input for human collaboration.

Core Features & Use Cases

Automated Event Discovery: Agents explore codebases to identify candidate domain events, aggregates, and state changes.
Assumption Surfacing: Explicitly captures and documents assumptions made about domain boundaries and contracts.
Structured Output: Generates YAML files conforming to a schema, ready for human review and downstream processing by tools like /formalize.
Use Case: Before a multi-team Event Storming session, each participant runs /storm-prep for their domain to generate a set of candidate events and assumptions, ensuring a common starting point for the collaborative modeling session.

Quick Start

Run the storm-prep skill with your domain scope and project goal to begin discovering domain events.

Frequently Asked Questions about storm-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I discover domain events for Event Storming from an existing codebase?▼

Use storm-prep to automate domain event discovery by analyzing your codebase for state changes, command flows, and integration points, outputting structured YAML for collaborative modeling sessions.

What is the best way to prepare for a multi-team Event Storming session?▼

Run domain analysis on each subsystem to generate candidate events and boundary assumptions, ensuring a common starting point for collaborative modeling and downstream formalization workflows.

Can I surface boundary assumptions and integration points using domain-driven design exploration?▼

Domain-driven design exploration explicitly captures and documents assumptions about domain boundaries and contracts during codebase analysis, making implicit integration points visible before formal modeling.

How do I generate YAML from code exploration for downstream DDD formalization?▼

Code exploration generates YAML files conforming to a schema, ready for human review and downstream processing by formalization tools, mapping identified aggregates and state changes into structured formats.

Does automated event discovery replace collaborative Event Storming sessions?▼

Automated event discovery prepares structured input by surfacing candidate events and assumptions, ensuring participants share a common analytical starting point for collaborative Event Storming sessions.