ddd-playbook

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

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 12, 2025⬇️1downloads

When & Why to Use This Skill

The DDD Playbook is a specialized Claude skill designed to guide developers and architects through the Domain-Driven Design (DDD) discovery process. It provides a structured framework for defining ubiquitous language, establishing bounded contexts, and modeling aggregates and invariants specifically for the ToDo domain, ensuring a robust and maintainable software architecture.

Use Cases

  • Domain Modeling: Systematically defining business entities, aggregates, and invariants to create a clean and scalable system design for task management applications.
  • Ubiquitous Language Development: Building and maintaining a project-specific glossary to align technical implementation with business requirements and terminology.
  • Architectural Training: Serving as a guided exercise for developers to learn and apply DDD principles in a controlled, practical environment using the ToDo domain as a reference.
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.