What problem does it solve? When building a new system or substantially changing an existing one, teams often jump into implementation without shared understanding, leading to costly rework. This Skill turns vague requirements into a traceable design covering domain models, boundaries, data flows, and documented tradeoffs. ## Core Features & Use Cases - Domain Discovery: Identifies actors, commands, events, entities, invariants, and failure outcomes, optionally using EventStorming when workflows are unclear. - Progressive Views: Produces only the views the task requires—context, containers, critical flows, data, and deployment—each at a consistent abstraction level. - Explicit Tradeoffs: Compares the simplest option against viable alternatives across complexity, reliability, cost, operability, and reversibility, recording assumptions and invalidation signals. - Use Case: Given requirements for a new order-processing platform, use this Skill to frame scope and constraints, model the domain, design critical flows with retry and timeout behavior, and deliver a concise design document with decisions, risks, and migration steps. ## Quick Start Use the system-design skill to turn these requirements for a notification service into a design with domain model, key flows, and tradeoffs.
