What problem does it solve? Deciding whether and how to adopt Domain-Driven Design is difficult: teams often over-engineer simple CRUD systems or under-model complex domains. This Skill provides a viability check, a staged workflow from strategic modeling to tactical implementation, and routing to specialized skills for CQRS, event sourcing, sagas, and projections. ## Core Features & Use Cases - Viability Assessment: Applies a four-criteria check (business complexity, model collisions, unstable integrations, auditability needs) before committing to full DDD. - Staged Deliverables: Produces strategic artifacts first (subdomain maps, bounded contexts, ubiquitous language glossary), then tactical artifacts (aggregates, value objects, domain events), with a checklist in references/ddd-deliverables.md. - Skill Routing: Directs follow-up work to specialized skills such as ddd-strategic-design, ddd-context-mapping, cqrs-implementation, event-sourcing-architect, and saga-orchestration. - Use Case: A team building a billing platform asks whether full DDD is justified; the Skill runs the viability check, defines the bounded contexts and glossary, then routes evented architecture questions to the appropriate specialist skills. ## Quick Start Ask the assistant to assess whether your project should adopt Domain-Driven Design and to list the strategic artifacts your team must produce this week.
