domain-driven-design

Plan and route Domain-Driven Design work from strategic modeling to tactical implementation and evented architecture patterns.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/domain-driven-design/SKILL.md

Quality

Content

57%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a competent orchestration/routing skill that provides a clear viability checklist and routing map for DDD work. Its main weaknesses are the lack of concrete, executable guidance (it delegates everything to sub-skills without showing what artifacts look like) and the absence of validation checkpoints in the workflow. The referenced sub-skills and template file cannot be verified since no bundle files are provided.

Suggestions

Add a concrete example of at least one output artifact (e.g., a sample bounded context map or subdomain classification table) so Claude knows what to produce, not just where to route.

Include explicit validation/checkpoint steps in the workflow, such as 'Confirm viability assessment with the user before proceeding to strategic modeling' and 'Review produced artifacts against the success criteria before routing to tactical patterns.'

Provide the referenced `references/ddd-deliverables.md` as a bundle file, or inline a minimal template showing expected deliverable structure.

Make the routing map more actionable by briefly describing what each sub-skill produces (e.g., '@ddd-strategic-design → produces subdomain map and bounded context diagram').

Dimension	Reasoning	Score
Conciseness	The skill is fairly lean and avoids explaining what DDD is to Claude. The 'Use this skill when' and 'Do not use this skill when' sections are useful but slightly verbose—some bullet points could be tightened. Overall efficient with minor trimming opportunities.	4 / 5
Actionability	The skill provides a viability checklist and a routing map, which are concrete decision aids. However, there is no executable code, no concrete command sequences, and the routing references (e.g., `@ddd-strategic-design`) are opaque without further context. The guidance is structured but remains at a high-level orchestration layer without showing what the actual artifacts look like or how to produce them.	3 / 5
Workflow Clarity	There is a rough sequence (viability check → strategic artifacts → routing → success criteria), but the steps lack explicit validation checkpoints or feedback loops. Step 4 mentions 'define success criteria and evidence' but doesn't specify how to validate outputs or what to do if the viability check is borderline. For a planning/routing skill this is acceptable but not strong.	3 / 5
Progressive Disclosure	The skill references `references/ddd-deliverables.md` and multiple sub-skills via `@` routing, which is good progressive disclosure in principle. However, no bundle files are provided, so we cannot verify these references exist. The routing map is well-signaled but the single template reference is buried in a conditional sentence rather than clearly listed. The content is all inline with no actual separation into supporting files.	3 / 5
	Total	13 / 20 Passed

Description

45%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear domain (DDD) but remains at a high abstraction level, using category names rather than concrete actions. It lacks a 'Use when...' clause and misses common trigger terms and abbreviations that users would naturally employ when seeking DDD guidance.

Suggestions

Add a 'Use when...' clause with trigger terms like 'DDD', 'bounded contexts', 'aggregates', 'domain events', 'event sourcing', 'CQRS'

Replace abstract categories with concrete actions, e.g., 'Creates bounded context maps, defines aggregates and entities, designs domain events and event flows'

Include the abbreviation 'DDD' and common synonyms/related terms users would naturally mention

Dimension	Reasoning	Score
Specificity	Names the domain (Domain-Driven Design) and mentions a few areas (strategic modeling, tactical implementation, evented architecture patterns), but these are still fairly abstract categories rather than concrete actions like 'create bounded context maps' or 'define aggregates'.	3 / 5
Completeness	Has a vague 'what' (plan and route DDD work) but no explicit 'when' clause. There's no 'Use when...' guidance, and the description doesn't clearly explain what concrete outputs or actions the skill produces.	2 / 5
Trigger Term Quality	Includes 'Domain-Driven Design' and related terms like 'strategic modeling', 'tactical implementation', and 'evented architecture', but misses common natural phrases users would say like 'DDD', 'bounded contexts', 'aggregates', 'event sourcing', 'CQRS', 'domain events'.	3 / 5
Distinctiveness Conflict Risk	Domain-Driven Design is a fairly specific niche that wouldn't easily conflict with most other skills. However, 'evented architecture patterns' could overlap with general architecture skills, and 'tactical implementation' is broad enough to potentially conflict with coding skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/domain-driven-design/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.