Dev10x:ddd-workshop

Conduct structured DDD workshops to uncover domain events, commands, actors, policies, aggregates, and bounded contexts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ddd-workshop-brave-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dev10x:ddd-workshop
Source: https://github.com/Brave-Labs/dev10x/tree/main/skills/ddd
Command: npx skills add https://github.com/Brave-Labs/dev10x --skill dev10x-ddd-workshop-brave-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain-driven design workshops help teams rapidly discover domain boundaries, model architectures, and governance by guiding participants through event storming patterns, archetypes, and artifact generation.

Core Features & Use Cases

  • Guided event storming covering domain events, commands, actors, policies, aggregates, bounded contexts, and value objects.
  • Structured orchestration with the Step 1–6 workflow: load context, exploration, stress testing, decision capture, produce artifacts, and quality checklist.
  • Auto-creation and tracking of workshop artifacts including decisions.md and workshops/NNN-topic.md with minimal friction.
  • Modes to start new workshops, continue existing domains, or apply archetypes while referencing governance materials.

Quick Start

Start a new DDD workshop by loading context and following the Step 1–Step 6 workflow to complete the session.

Frequently Asked Questions about Dev10x:ddd-workshop

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

FAQPage Schema
How do I run an event storming workshop to model bounded contexts and aggregates?

Use a structured Step 1–6 workflow to orchestrate event storming sessions: load context, explore domain events and commands, stress test, capture decisions, produce artifacts, and run quality checks to model bounded contexts and aggregates.

What is domain-driven design workshop orchestration and how does it capture architecture decisions?

Domain-driven design workshop orchestration guides teams through event storming to uncover domain events, commands, and policies, while automatically capturing architecture decisions in a tracked decisions.md file.

Can I continue modeling an existing domain model or do I need to start a new DDD workshop from scratch?

You can continue modeling an existing domain model without starting from scratch. The workshop supports continuation modes to load existing contexts and resume stress-testing architecture and governance.

What artifacts does a DDD workshop generate for domain modeling and governance?

A DDD workshop generates structured artifacts including a decisions.md file for governance tracking and numbered workshop records under workshops/NNN-topic.md to document domain events, commands, actors, and policies.

When should I stress-test architecture during domain-driven design modeling?

You should stress-test architecture during the Step 3 phase of domain-driven design modeling to validate seam identification, governance boundaries, and aggregate coherence before final artifact generation.

Do I need prior event storming experience to conduct a structured DDD workshop?

No prior event storming experience is required to conduct a structured DDD workshop, as the Step 1–6 workflow provides guided orchestration covering archetypes, domain events, commands, and bounded contexts.