How do I install the Architecture Ddd skill?

Run npx skillmds@latest add planifest/architecture-ddd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Ddd safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Ddd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Ddd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Architecture Ddd?

planifest (@planifest) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Ddd by planifest — Agent Skill

Name: Architecture Ddd
Author: planifest

Architecture Ddd

Domain-driven design workflow for bounded context partitioning, aggregate design, and context mapping in complex domains. Use when domain complexity or organizational scaling requires explicit model boundaries; do not use for small CRUD domains without competing language models.

planifest c864590 2 files · 13.6 KB Updated Sep 17, 2026

File contents

Architecture DDD

Overview

Use this skill to model complex domains so teams can evolve behavior without constant cross-team coupling.

Scope Boundaries

Domain language differs across teams or subsystems.
Invariants are hard to maintain because boundaries are unclear.
A single model is causing conflicting meanings and high coordination cost.

Core Judgments

Bounded context cuts: where language and invariants legitimately diverge.
Aggregate boundaries: where consistency must be immediate versus eventual.
Context integration style: ACL, conformist, published language, or shared kernel.
Ownership model: which team can change which part without global coordination.

Practitioner Heuristics

Bound contexts by change patterns and invariants, not by database tables.
Aggregates should protect invariants with minimal transactional scope.
Cross-context communication should exchange explicit contracts, not internal models.
In dynamic languages, model entities/value objects with explicit typed schemas instead of broad maps that require repetitive casting.

Workflow

Build ubiquitous language per domain area and identify conflicting terms.
Partition bounded contexts by invariants, autonomy, and change cadence.
Design aggregates with clear consistency and lifecycle rules.
Define context map and integration contracts between contexts.
Identify anti-corruption needs and translation responsibilities.
Document residual ambiguity and model evolution triggers.

Common Failure Modes

"DDD" applied as folder naming without boundary behavior changes.
Aggregates oversized, causing lock contention and slow writes.
Shared database schema used as de facto integration API.

Failure Conditions

Stop when bounded contexts cannot be separated by language/invariant boundaries.
Stop when aggregate consistency needs conflict with transaction feasibility.
Escalate when cross-context contracts remain uncontrolled.

---name: architecture-ddddescription: Domain-driven design workflow for bounded context partitioning, aggregate design, and context mapping in complex domains. Use when domain complexity or organizational scaling requires explicit model boundaries; do not use for small CRUD domains without competing language models.---# Architecture DDD## OverviewUse this skill to model complex domains so teams can evolve behavior without constant cross-team coupling.## Scope Boundaries- Domain language differs across teams or subsystems.- Invariants are hard to maintain because boundaries are unclear.- A single model is causing conflicting meanings and high coordination cost.## Core Judgments- Bounded context cuts: where language and invariants legitimately diverge.- Aggregate boundaries: where consistency must be immediate versus eventual.- Context integration style: ACL, conformist, published language, or shared kernel.- Ownership model: which team can change which part without global coordination.## Practitioner Heuristics- Bound contexts by change patterns and invariants, not by database tables.- Aggregates should protect invariants with minimal transactional scope.- Cross-context communication should exchange explicit contracts, not internal models.- In dynamic languages, model entities/value objects with explicit typed schemas instead of broad maps that require repetitive casting.## Workflow1. Build ubiquitous language per domain area and identify conflicting terms.2. Partition bounded contexts by invariants, autonomy, and change cadence.3. Design aggregates with clear consistency and lifecycle rules.4. Define context map and integration contracts between contexts.5. Identify anti-corruption needs and translation responsibilities.6. Document residual ambiguity and model evolution triggers.## Common Failure Modes- "DDD" applied as folder naming without boundary behavior changes.- Aggregates oversized, causing lock contention and slow writes.- Shared database schema used as de facto integration API.## Failure Conditions- Stop when bounded contexts cannot be separated by language/invariant boundaries.- Stop when aggregate consistency needs conflict with transaction feasibility.- Escalate when cross-context contracts remain uncontrolled.

Frequently asked questions