domain-driven-design-planner

Name: domain-driven-design-planner
Availability: InStock
Author: balsm-health

Assess DDD suitability and guide strategic modeling and implementation.

2|Updated Jun 5, 2026

Search Tags:#architecture #ddd #modeling #domain-driven-design #bounded-context

Ready to run

npx skills add https://github.com/balsm-health/Balsm-AI --skill domain-driven-design-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-driven-design-planner
Source: https://github.com/balsm-health/Balsm-AI/tree/main/plugin/skills/domain-driven-design-planner
Command: npx skills add https://github.com/balsm-health/Balsm-AI --skill domain-driven-design-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps determine the viability of full Domain-Driven Design (DDD) adoption and guides the planning and implementation of DDD work.

Core Features & Use Cases

Viability Check: Assess whether full DDD is appropriate for a project.
Strategic Modeling: Produce strategic artifacts like subdomains, bounded contexts, and language glossaries.
Routing Map: Direct tasks to specialized skills for strategic design, tactical code modeling, evented architecture, and more.
Output Requirements: Ensure scope, assumptions, current stage, artifacts produced, risks, and next steps are documented.
Use Case: Decide if a billing platform should adopt full DDD and plan the necessary steps.

Quick Start

Run a viability check for DDD using the 'domain-driven-design-planner' skill and follow the routing map to the appropriate next skill.

Frequently Asked Questions about domain-driven-design-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I know if my project needs full domain-driven design?▼

Domain-driven design viability requires assessing project complexity. This skill runs a check to determine if full DDD is appropriate and documents scope, assumptions, risks, and next steps for your business domain modeling.

How do I identify bounded contexts and subdomains for complex architecture?▼

Identifying bounded contexts requires strategic modeling artifacts. This skill guides the production of subdomains, bounded contexts, and language glossaries to structure complex business domains effectively.

What is the best way to plan domain-driven design implementation steps?▼

Planning DDD implementation requires a routing map. This skill directs tasks to specialized skills for strategic design, tactical code modeling, and evented architecture, ensuring documented steps from current stage to final artifacts.

Can I use domain-driven design for evented architecture planning?▼

Domain-driven design supports evented architecture planning through strategic domain thinking. It provides a routing map to specialized skills for evented systems and complex business domain modeling.

When should I avoid adopting full domain-driven design for my software?▼

Avoid full domain-driven design when the viability check determines insufficient domain complexity. The skill evaluates project suitability, documenting assumptions and risks to prevent over-engineering simple business domains.