Domain Driven Design

What it does

This skill analyzes complex problems using domain-driven design (DDD) principles to generate clear, actionable solutions and system architectures. It helps determine if full DDD is appropriate for a given situation and connects strategic design decisions to implementation patterns. The skill produces key artifacts like subdomains, bounded contexts, and language glossaries to guide development efforts.

When to use it

• When modeling complex business domains with explicit boundaries is required.
• To assess whether the added complexity of full DDD is justified for a project.
• When planning architectures involving CQRS, event sourcing, sagas, or projections derived from domain needs.
• When multiple teams are causing model collisions or integration contracts are unstable.

Key capabilities

• Performs a viability check to determine if full DDD is appropriate.
• Produces strategic artifacts: subdomains, bounded contexts, and language glossary.
• Routes tasks to specialized skills (e.g., @ddd-context-mapping, @cqrs-implementation).
• Defines success criteria and evidence for each stage of the design process.
• Provides a routing map to other relevant skills.

Example prompts

• "Use @domain-driven-design to assess if this billing platform should adopt full DDD."
• "Then route to the right next skill and list artifacts we must produce this week."
• "What are the strategic artifacts needed for our new inventory management system?"

Tips & gotchas

• This skill requires access to domain knowledge or a proxy product expert.
• It does not replace direct workshops with domain experts or provide framework-specific code generation.
• Avoid using this skill for simple CRUD applications – it's intended for complex business domains.