task-ui-discovery

To convert event-storming documentation into UI specs, you process the workshop output to generate a structured screen inventory, map user flows, and produce presenter specifications for implementation and testing.

Generating a screen inventory from event-storming outputs involves analyzing the documented domain events to extract, organize, and prioritize screens and UI elements within a specific bounded context.

Yes, you can create presenter specifications directly from a bounded context definition by delegating event-storming analysis to extract structured presenter contracts for frontend implementation and automated testing.

During UI discovery, user flows map to screens by tracing key user journeys and transitions extracted from event-storming documentation, clarifying behavior and edge cases across the generated screen inventory.

Yes, an event-storming document is the required input to generate user flows and screen lists, while an optional bounded context name can be provided to narrow the frontend design discovery scope.

You should not use event-storming for UI design discovery if you lack documented domain events, as the process relies entirely on converting existing event-storming outputs into actionable UI artifacts.