system-design

To translate vague requirements into an event-driven architecture, this Skill uses EventStorming to identify design goals and constraints, producing a phased design catalog with Mermaid diagrams. It progressively elaborates system design across five phases.

Visualizing system design phases with Mermaid diagrams is achieved by generating big-picture diagrams, process diagrams, and data models inline within a catalog README. This allows immediate preview of the event-driven architecture and flows.

To start an EventStorming session, you provide a brief for your new system. The Skill then initiates a design session, asking questions and generating a design catalog under docs/design-catalog using progressive elaboration.

No, the system design catalog strictly maintains design-only artifacts and avoids implementation details. It focuses entirely on architectural design, event flows, and data models rather than code generation.

The five phases of progressive elaboration for system architecture are Requirements, Big Picture, Processes, Data/Flows, and Integration. Each phase builds upon the previous to elaborate the event-driven design.

You can use this EventStorming-driven design catalog for both new systems and major redesigns. It provides ready-to-activate design guidance to navigate architectural constraints and translate updated requirements into data flows.