ddd-playbook

Guides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill acts as a specialized consultant for Domain-Driven Design (DDD) discovery, specifically optimized for the ToDo domain. It streamlines the architectural process by guiding users through the creation of a ubiquitous language, defining bounded contexts, and structuring aggregates with strict business invariants. By following a structured playbook, it ensures that software models remain clean, maintainable, and aligned with business logic.

Use Cases

  • Domain Modeling: Systematically defining core entities, value objects, and aggregates for task management systems to ensure architectural integrity.
  • Technical Documentation: Generating and updating a glossary of ubiquitous language to bridge the communication gap between developers and domain experts.
  • Constraint Enforcement: Defining and validating business invariants and use-case contracts to prevent invalid system states during the design phase.
  • Architectural Training: Serving as a practical exercise or 'playbook' for developers to learn and apply DDD principles in a controlled, specific domain.
nameddd-playbook
descriptionGuides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants.
allowed-toolsRead, Grep, Glob, Edit, Write

DDD Playbook (ToDo training)

  1. Update glossary first.
  2. Keep one bounded context: "Todo Management".
  3. Propose a minimal aggregate and max 5 invariants at a time.
  4. For each capability, update model + invariants + use-case contract. Never introduce advanced patterns unless asked.