ddd-pm

Translate business requirements into a Ubiquitous Language glossary and domain event triggers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tojoolivier/claude-config --skill ddd-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ddd-pm
Source: https://github.com/tojoolivier/claude-config/tree/main/skills/ddd-pm
Command: npx skills add https://github.com/tojoolivier/claude-config --skill ddd-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating business requirements into a precise, shared domain language to align business and technical teams. It clarifies terminology, reduces miscommunication, and accelerates discovery by providing a living glossary of domain concepts.

Core Features & Use Cases

  • Glossary extraction: derive a Ubiquitous Language directly from requirements.
  • Domain classification: identify Core Domain, Supporting Domain, and Generic Domain to guide prioritization.
  • Event trigger formulation: generate Domain Event candidates that reflect business rules and triggers.

Quick Start

Analyze a recent business requirement and produce a living glossary plus a set of domain event triggers.

Frequently Asked Questions about ddd-pm

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

FAQPage Schema
How do I translate business requirements into a ubiquitous language for domain modeling?

To translate business requirements into a ubiquitous language, you analyze the requirements to extract a precise, shared glossary of domain concepts that align business and technical teams to reduce miscommunication.

What is the best way to identify core domain and supporting domain from business rules?

Identifying core domain and supporting domain from business rules involves classifying domain concepts during requirements analysis to guide prioritization and clarify which areas hold fundamental strategic value.

How do I formulate domain event triggers from business requirements?

Formulating domain event triggers from business requirements requires analyzing business rules to generate domain event candidates that reflect specific operational triggers, providing a clear set of events to guide architecture and development.

When do I need ubiquitous language extraction for requirements analysis?

You need ubiquitous language extraction for requirements analysis when aligning business and technical teams, clarifying terminology, and accelerating discovery by providing a living glossary of domain concepts to guide architecture work.

Does domain modeling with ubiquitous language reduce miscommunication between business and code?

Domain modeling with ubiquitous language reduces miscommunication by producing a living glossary that the business and code must share, ensuring both teams operate on a precise, mutually understood set of domain concepts and event triggers.