ddd-decompose

Identifying bounded contexts and aggregates during system decomposition requires a structured interview process that guides you through extracting domain events and defining clear boundaries. This Skill provides that guided workflow to map complex domains accurately.

Domain-driven design decomposition is needed when designing a new system with multiple teams or refactoring a monolith into bounded contexts. It helps structure complex systems by clarifying domain events, aggregates, and context boundaries.

Creating a DDD context map involves analyzing your domain to extract bounded contexts and relationships. This Skill walks you through an interview-style process to generate context maps and optional ForgePlan artifacts for artifact graph integration.

Yes, you need a solid understanding of DDD principles before starting. The decomposition process relies on interview-style input and requires foundational knowledge of bounded contexts, aggregates, and domain events to produce accurate architecture outputs.

The best way to map domain events across multiple teams is using a guided DDD decomposition process that standardizes the identification of bounded contexts. This ensures consistent context maps and domain event tracking across the entire system architecture.

Yes, you can generate ForgePlan artifacts like Epics, PRDs, and Specs directly from your DDD bounded contexts. The decomposition process outputs a DDD context map and optional ForgePlan artifacts for seamless artifact graph integration.