Skills ddd-strategic-design
📦

ddd-strategic-design

Content revision r1 Safe ⚙️ External commands

Design Clear DDD Context Boundaries

Complex domains often produce unclear service boundaries, inconsistent terms, and disputed ownership. This skill creates subdomain maps, context catalogs, glossaries, and documented boundary decisions.

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 "ddd-strategic-design" from https://skillstore.io/skills/sickn33-ddd-strategic-design.md and its manifest at https://skillstore.io/api/skills/sickn33-ddd-strategic-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-ddd-strategic-design.md Signed manifest GET /api/skills/sickn33-ddd-strategic-design/manifest Signed lockfile GET /api/skills/sickn33-ddd-strategic-design/lockfile

Test it

Using "ddd-strategic-design". Classify pricing, identity, search, and checkout for a retail platform.

Expected outcome:

  • Pricing: Core, because pricing strategy can create differentiated business value.
  • Identity: Supporting, because it enables commerce without defining the retail advantage.
  • Search: Classification needs stakeholder evidence about differentiation and customer value.
  • Checkout: Supporting or core, depending on whether the purchase experience creates measurable advantage.

Using "ddd-strategic-design". Separate the meanings of order across checkout and fulfillment.

Expected outcome:

  • Checkout Order: A confirmed purchase request accepted after payment authorization.
  • Fulfillment Order: An operational instruction to reserve, pack, and dispatch purchased items.
  • Boundary decision: Each context owns its definition and translates the term at integration points.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

Both static findings are false positives caused by Markdown backticks, not shell execution. The prompt-only skill contains no executable code or suspicious instructions.

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

Risk Factors

⚙️ External commands (2)
SKILL.md:32 SKILL.md:43-46
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-ddd-strategic-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-ddd-strategic-design/security.svg)](https://skillstore.io/skills/sickn33-ddd-strategic-design?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-ddd-strategic-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). ddd-strategic-design security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-ddd-strategic-design/audits/5

BibTeX citation

@techreport{sickn33-sickn33-ddd-strategic-design-2026, author = {sickn33}, title = {ddd-strategic-design security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-ddd-strategic-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: "ddd-strategic-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-ddd-strategic-design/audits/5" identifiers: - type: other value: "skillstore:sickn33-ddd-strategic-design:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Decompose a monolith

Identify subdomains and bounded contexts before separating a monolithic application into independently owned services.

Align team ownership

Connect domain responsibilities, dependencies, and context boundaries to accountable engineering teams.

Standardize domain language

Create canonical definitions and expose terms that mean different things across business contexts.

Try These Prompts

Classify subdomains 
Classify these business capabilities as core, supporting, or generic subdomains: [capabilities]. Explain each classification and identify missing stakeholder information.
Define bounded contexts 
Propose bounded contexts for [domain]. For each context, describe its responsibility, owner, consistency boundary, upstream dependencies, and downstream consumers.
Build a shared glossary 
Create a ubiquitous language glossary from [domain notes]. Include canonical terms, definitions, owning contexts, ambiguous synonyms, and anti-terms.
Design the domain landscape 
Analyze [business description] and produce a subdomain table, bounded context catalog, glossary, team ownership proposal, and boundary decisions with rationale. State assumptions and conflicts.

Best Practices

  • Provide real business capabilities, workflows, constraints, and current ownership before requesting boundaries.
  • Validate every classification and term with domain experts from the affected contexts.
  • Record assumptions and unresolved conflicts beside each proposed boundary decision.

Avoid

  • Do not treat technical layers or database tables as business subdomains.
  • Do not force one universal definition when a term has valid context-specific meanings.
  • Do not implement proposed boundaries before stakeholders validate responsibilities and ownership.

Frequently Asked Questions

What information should I provide?
Provide business capabilities, important workflows, domain terms, current systems, team ownership, dependencies, and known consistency requirements.
Does this skill generate implementation code?
No. It produces strategic design artifacts that should guide later tactical design and implementation.
Can it classify a subdomain without stakeholder input?
It can propose a classification, but domain experts must validate business differentiation, value, and operational importance.
How are bounded contexts selected?
The skill considers responsibilities, consistency needs, ownership, dependencies, and differences in domain language.
Can it help split a monolith?
Yes. It can propose domain boundaries and ownership before teams choose technical extraction strategies.
What should happen after strategic design?
Validate the artifacts, record boundary decisions, then perform tactical design for aggregates, events, interfaces, and implementation details.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/ddd-strategic-design

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

12 downloads · 90 views

File structure

📁 references/

📄 strategic-design-template.md

📄 SKILL.md