ddd-planning

Plan a Domain-Driven Design project through six phase gates from discovery to implementation.

Updated Feb 24, 2026

Search Tags:#planning #architecture #ddd #governance #context-map #event-storming

Ready to run

npx skills add https://github.com/AymanKastali/pydentity --skill ddd-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd-planning
Source: https://github.com/AymanKastali/pydentity/tree/main/.claude/skills/ddd-planning
Command: npx skills add https://github.com/AymanKastali/pydentity --skill ddd-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a Domain-Driven Design project can be daunting without a structured, gate-driven approach that links discovery to implementation and guarantees verifiable progress.

Core Features & Use Cases

Structured discovery workflow: Facilitates knowledge crunching, ubiquitous language development, and ambiguity tracking to build a shared domain model.
Event Storming & Context Mapping: Guides teams through identifying domain events, commands, aggregates, policies, read models, and bounded contexts to shape architecture.
Phase-gated governance: Enforces six gates from discovery to implementation, delivering an actionable roadmap and measurable milestones.
Artifacts & governance artifacts: Produces domain narratives, glossary entries, context maps, and planning artifacts to anchor decision making.

Quick Start

Initiate a DDD planning session by outlining a domain problem and running through all six phased gates.

Frequently Asked Questions about ddd-planning

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

FAQPage Schema

How do I plan a Domain-Driven Design project from discovery to implementation?▼

To plan a DDD project, this skill applies a gate-driven process guiding teams from domain discovery to an actionable implementation roadmap. It enforces six mandatory gates to ensure verifiable progress and architectural alignment.

What is the best way to facilitate Event Storming and Context Mapping for my architecture?▼

Facilitating Event Storming and Context Mapping is handled by guiding teams to identify domain events, commands, aggregates, policies, and bounded contexts. This process shapes your architecture and produces verifiable planning artifacts.

How does phase-gated governance work in DDD architectural planning?▼

Phase-gated governance in DDD planning enforces six distinct gates from discovery to implementation. It delivers measurable milestones and an actionable roadmap, ensuring architectural decisions remain verifiable and aligned with domain analysis.

Do I need a structured ubiquitous language and glossary before DDD implementation?▼

Developing a ubiquitous language and glossary is part of the structured discovery workflow before implementation. It facilitates knowledge crunching and ambiguity tracking to build a shared domain model anchored by governance artifacts.

Can I use this DDD planning approach for any software team doing domain analysis?▼

Yes, this DDD planning approach applies directly to software teams engaging in domain analysis, Event Storming, and architectural planning. It ensures alignment to mandatory gates, artifacts, and governance disciplines regardless of the specific domain.