system-design

To convert vague requirements into system architecture, use EventStorming to elicit domain events and actors, then generate a standardized design catalog. This produces Mermaid diagrams and markdown files for progressive elaboration without implementation assumptions.

EventStorming works by guiding collaborative elicitation of domain events, commands, actors, and systems to surface requirements and ambiguities. It enforces event-driven thinking and question-driven elicitation to produce high-level and detailed system artifacts for cross-functional workshops.

Yes, you can generate Mermaid-native artifacts automatically from requirements. The process produces token-efficient visual artifacts including big-picture timelines, process diagrams, ERDs, state charts, and sequence diagrams stored in a standardized docs/design-catalog directory layout.

This approach requires no specific frameworks or dependencies, focusing entirely on event-driven design thinking and Mermaid diagrams. It operates under non-implementation constraints, making it suitable for architecture planning and cross-functional workshops without locking you into specific technologies.

The best way to document data models and integration flows is to create a standardized docs/design-catalog directory with embedded Mermaid files. This includes separate subdirectories for processes, data models, and flows, producing reproducible artifacts that support handoff to implementation planning.

You should not use event-driven design catalogs when implementation details are already fully specified or when progressive elaboration of requirements is unnecessary. This approach deliberately enforces non-implementation constraints, making it unsuitable for projects needing immediate code generation rather than design exploration.