About

Imported from aiskillstore/marketplace (skills/sickn33/domain-driven-design/SKILL.md). Install upstream with npx skills add aiskillstore/marketplace --skill domain-driven-design. Copyright stays with the author.

Domain-Driven Design

Name: domain-driven-design
Author: aiskillstore

Use this skill when

You need to model a complex business domain with explicit boundaries.
You want to decide whether full DDD is worth the added complexity.
You need to connect strategic design decisions to implementation patterns.
You are planning CQRS, event sourcing, sagas, or projections from domain needs.

Do not use this skill when

The problem is simple CRUD with low business complexity.
You only need localized bug fixes.
There is no access to domain knowledge and no proxy product expert.

Instructions

Run a viability check before committing to full DDD.
Produce strategic artifacts first: subdomains, bounded contexts, language glossary.
Route to specialized skills based on current task.
Define success criteria and evidence for each stage.

Viability check

Use full DDD only when at least two of these are true:

Business rules are complex or fast-changing.
Multiple teams are causing model collisions.
Integration contracts are unstable.
Auditability and explicit invariants are critical.

Routing map

Strategic model and boundaries: @ddd-strategic-design
Cross-context integrations and translation: @ddd-context-mapping
Tactical code modeling: @ddd-tactical-patterns
Read/write separation: @cqrs-implementation
Event history as source of truth: @event-sourcing-architect and @event-store-design
Long-running workflows: @saga-orchestration
Read models: @projection-patterns
Decision log: @architecture-decision-records

If templates are needed, open references/ddd-deliverables.md.

Output requirements

Always return:

Scope and assumptions
Current stage (strategic, tactical, or evented)
Explicit artifacts produced
Open risks and next step recommendation

Examples

Use @domain-driven-design to assess if this billing platform should adopt full DDD.
Then route to the right next skill and list artifacts we must produce this week.

Limitations

This skill does not replace direct workshops with domain experts.
It does not provide framework-specific code generation.
It should not be used as a justification to over-engineer simple systems.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/aiskillstore-marketplace-domain-driven-design/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

aiskillstore-marketplace-domain-driven-design.ocm.jsonjson

{
  "ocm": "1",
  "id": "aiskillstore-marketplace-domain-driven-design",
  "kind": "skill",
  "name": "domain-driven-design",
  "description": "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.",
  "publisher": "aiskillstore",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "ddd",
      "domain",
      "bounded-context",
      "architecture",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/aiskillstore/marketplace",
      "path": "skills/sickn33/domain-driven-design/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/aiskillstore/marketplace/blob/HEAD/skills/sickn33/domain-driven-design/SKILL.md",
      "key": "aiskillstore/marketplace/skills/sickn33/domain-driven-design/SKILL.md"
    }
  },
  "instructions": "# Domain-Driven Design\n\n## Use this skill when\n\n- You need to model a complex business domain with explicit boundaries.\n- You want to decide whether full DDD is worth the added complexity.\n- You need to connect strategic design decisions to implementation patterns.\n- You are planning CQRS, event sourcing, sagas, or projections from domain needs.\n\n## Do not use this skill when\n\n- The problem is simple CRUD with low business complexity.\n- You only need localized bug fixes.\n- There is no access to domain knowledge and no proxy product expert.\n\n## Instructions\n\n1. Run a viability check before comm",
  "cost": {
    "context_tokens": 552
  }
}

Fetch it by URL: GET /api/v1/registry/aiskillstore-marketplace-domain-driven-design/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.