Skills domain-driven-design
📦

domain-driven-design

Content revision r2 Safe ⚙️ External commands

Plan Domain-Driven Design Work

Complex domains need clear boundaries before implementation patterns are selected. This skill assesses DDD viability, defines strategic artifacts, and recommends focused next steps.

Supports: Claude Codex Code(CC)
📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "domain-driven-design" from https://skillstore.io/skills/sickn33-domain-driven-design.md and its manifest at https://skillstore.io/api/skills/sickn33-domain-driven-design/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-domain-driven-design.md Signed manifest GET /api/skills/sickn33-domain-driven-design/manifest Signed lockfile GET /api/skills/sickn33-domain-driven-design/lockfile

Test it

Using "domain-driven-design". Assess DDD for a billing platform with changing rules and several teams.

Expected outcome:

  • Recommendation: DDD is viable because rules change frequently and team models collide.
  • Strategic artifacts: subdomain map, bounded context map, ownership assignments, and billing glossary.
  • Next step: validate boundaries with billing experts before selecting tactical patterns.

Using "domain-driven-design". Plan evented deliverables for an order workflow spanning payments and fulfillment.

Expected outcome:

  • Current stage: evented architecture planning.
  • Required artifacts: CQRS rationale, event versioning policy, compensation matrix, and projection rebuild strategy.
  • Open risk: context ownership and failure recovery rules require domain confirmation.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All ten static findings are false positives caused by Markdown backticks around skill names, a local reference path, and a plain-text example. The reviewed files contain no executable commands or semantic security concerns.

2
Files scanned
100
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (10)
SKILL.md:43 SKILL.md:44 SKILL.md:45 SKILL.md:46 SKILL.md:47 SKILL.md:48 SKILL.md:49 SKILL.md:50 SKILL.md:52 SKILL.md:65-68
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-domain-driven-design/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-domain-driven-design/security.svg)](https://skillstore.io/skills/sickn33-domain-driven-design?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-domain-driven-design?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-domain-driven-design/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-domain-driven-design.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). domain-driven-design security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-domain-driven-design/audits/5

BibTeX citation

@techreport{sickn33-sickn33-domain-driven-design-2026, author = {sickn33}, title = {domain-driven-design security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-domain-driven-design/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "domain-driven-design security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-domain-driven-design/audits/5" identifiers: - type: other value: "skillstore:sickn33-domain-driven-design:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
41
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Assess DDD Adoption

Evaluate whether a complex product domain justifies full DDD before committing engineering resources.

Define Service Boundaries

Map subdomains, bounded contexts, ownership, and shared language for teams with overlapping models.

Plan Evented Architecture

Connect domain needs to CQRS, event sourcing, sagas, projections, and required governance artifacts.

Try These Prompts

Check DDD Viability 
Assess whether {system} needs full DDD. List assumptions, applicable viability criteria, risks, and the next recommended step.
Map the Domain 
Create a strategic DDD plan for {domain}. Identify subdomains, bounded contexts, ownership questions, glossary terms, and missing domain knowledge.
Choose Tactical Patterns 
Given {context_description}, recommend aggregates, invariants, value objects, domain events, repository contracts, and transaction boundaries. Explain unresolved risks.
Plan Evented Delivery 
Evaluate CQRS and event sourcing for {system}. Define justification, schema versioning, saga compensation, projection rebuilding, evidence, and specialist routing.

Best Practices

  • Run the viability check before adopting full DDD.
  • Complete strategic artifacts before selecting tactical or evented patterns.
  • Record assumptions, evidence, open risks, and measurable success criteria.

Avoid

  • Do not adopt DDD only because the architecture is fashionable.
  • Do not define aggregates before bounded contexts and language are understood.
  • Do not plan event sourcing without versioning, compensation, and rebuild strategies.

Frequently Asked Questions

When should I use this skill?
Use it for complex, changing domains that need explicit boundaries, cross-team alignment, or auditable business rules.
When is full DDD unnecessary?
Avoid full DDD for simple CRUD work, localized fixes, or domains without accessible expert knowledge.
Does this skill generate code?
No. It plans architecture artifacts and routes tactical work, but it does not generate framework-specific code.
What strategic artifacts does it recommend?
It recommends subdomain maps, bounded context maps, ownership assignments, a shared language glossary, and critical architecture decision records.
Does it require domain experts?
Yes. Reliable boundaries, language, and invariants require direct experts or a knowledgeable product representative.
Can it plan CQRS and event sourcing?
Yes. It evaluates domain need and identifies rationale, versioning, compensation, projection rebuilding, and specialist follow-up.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/domain-driven-design

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads · 122 views

File structure

📁 references/

📄 ddd-deliverables.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all