ddd-model

Identify and structure bounded contexts from a PRD into a multi-phase review workflow.

2|1|Updated Feb 4, 2026

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

Ready to run

npx skills add https://github.com/jrlangford/ddd-companion --skill ddd-model

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd-model
Source: https://github.com/jrlangford/ddd-companion/tree/main/skills/ddd-model
Command: npx skills add https://github.com/jrlangford/ddd-companion --skill ddd-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a system into bounded contexts and manage a multi-phase workflow for architecture design, persisting state across Claude Code sessions via a manifest.

Core Features & Use Cases

Phase-driven Bounded Context Review (context discovery, context mapping, FQBC generation, coherence review)
Manifest-based session persistence for multi-chat collaboration
Generated artifacts: bcr and fqbc documents, API binding templates, and traceability references
Supports onboarding and governance reviews with stepwise user validation

Quick Start

Provide a PRD and run /ddd-model to begin Phase 1 of the Bounded Context Review workflow.

Frequently Asked Questions about ddd-model

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

FAQPage Schema

How do I decompose a system into bounded contexts from a PRD?▼

You can decompose a system into bounded contexts by providing a Product Requirements Document (PRD) to initiate a multi-phase workflow that handles context discovery, context mapping, and coherence review.

What is domain-driven design context mapping and when do I need it?▼

Domain-driven design context mapping identifies relationships between bounded contexts. You need it when structuring complex architectures to generate API binding templates and traceability links for production-ready systems.

How do I persist architecture workflow state across multiple Claude Code chat sessions?▼

You can persist architecture workflow state across multiple Claude Code chat sessions using a manifest-based session persistence mechanism that stores artifacts and supports resuming interactions.

Can I generate API binding templates and traceability links for bounded contexts?▼

Yes, you can generate API binding templates and traceability references as workflow artifacts, ensuring they align with provided project conventions during the Fully Qualified Bounded Context (FQBC) generation phase.

Does the bounded context review workflow require any specific dependencies or components?▼

The bounded context review workflow operates with no external dependencies or components, requiring only a PRD and project conventions to execute its authorization pattern and stepwise user validation.

What are the limitations of using a manifest for domain-driven design session persistence?▼

The manifest enforces an authorization pattern and writes artifacts directly, meaning session persistence is tightly coupled to the manifest structure and requires stepwise user validation to proceed through each phase.