What problem does it solve? Turning a rough system idea into a rigorous Domain-Driven Design specification normally requires days of architecture work. This Skill produces a complete strategic design document — from requirements through Event Storming to a full TypeScript API spec — in a single structured workflow. ## Core Features & Use Cases - Full Strategic Pipeline: Generates all 7 sections of a DDD spec: high-level requirements, Event Storming with emoji markers, screens & commands tables, Bounded Context separation, Context Mapping with ASCII diagrams, design decisions, and a technical API specification. - Type-Safe API Contracts: Produces Input/Output/Errors TypeScript type definitions for every screen (Tnn) and command (Cnn), with shared enums, discriminated unions, and domain event annotations. - Automated Self-Review: Runs a structured R1–R5 review checklist (completeness, language, type safety, internal consistency, formatting) and fixes issues before delivering the document. - Use Case: Describe a billing platform idea and receive a 2000–4000 line Markdown spec covering Bounded Contexts, integration events, error code glossaries, and per-command TypeScript contracts ready for implementation. ## Quick Start Ask the assistant to create a full DDD specification document for your system idea, describing the actors, key domain concepts, and main operations.
