What is the difference between Strategic and Tactical design in this skill?

Strategic design focuses on high-level business domains and relationships (Context Maps), while Tactical design focuses on implementation patterns like Aggregates and Repositories.

What documents can the DDD Planning skill analyze?

The skill can analyze screen definitions, database schemas, and business requirement documents to identify and extract domain entities and logic.

Does it support code generation for specific languages?

Yes, it currently provides specialized templates for generating Kotlin DDD boilerplate, including Aggregates, Entities, and Domain Events.

Can this skill help with microservices transition?

Absolutely. It uses Strategic Design patterns like Context Mapping and Bounded Context definition which are critical for identifying service boundaries.

DDD Architect & Planner

Name: DDD Architect & Planner
Author: jskjw157

byjskjw157

API Development

Guides the full Domain-Driven Design lifecycle from strategic context mapping to tactical Kotlin code generation.

About

The DDD Planning skill empowers developers and architects to implement robust Domain-Driven Design (DDD) principles within their projects. It analyzes existing documentation such as screen definitions and database schemas to extract domain logic, define Bounded Contexts, and establish a Ubiquitous Language. Whether you are performing strategic mapping for microservices or generating tactical Kotlin boilerplate for Aggregates and Entities, this skill provides standardized templates and domain-specific guidance to ensure your software architecture stays aligned with complex business requirements.

Key Features

0 GitHub stars
Tactical modeling for Aggregates, Entities, and Value Objects
Production-ready Kotlin DDD boilerplate code generation
Strategic design for Bounded Contexts and Context Mapping
Automated domain term extraction from project documentation
Structured Event Storming support and documentation templates

Use Cases

Generating standardized domain-layer code for Kotlin projects
Defining boundaries and relationships for microservices architectures
Extracting domain models from legacy database schemas and UI specs

About

Key Features

0 GitHub stars
Tactical modeling for Aggregates, Entities, and Value Objects
Production-ready Kotlin DDD boilerplate code generation
Strategic design for Bounded Contexts and Context Mapping
Automated domain term extraction from project documentation
Structured Event Storming support and documentation templates

Use Cases

Generating standardized domain-layer code for Kotlin projects
Defining boundaries and relationships for microservices architectures
Extracting domain models from legacy database schemas and UI specs