Review ddd

Skill kt3k/skills/skills/review-ddd

Skills for developing software carefully and steadily. Plan tasks, review code, and refine design to improve overall quality.

Install

npx -y skills add kt3k/skills --skill review-ddd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Review code base from the viewpoint of Domain Driven Design (DDD) specialist. Evaluate how core business logics are well organized in terms of DDD principle.

SKILL.md

2.9 KB, as published. Nobody here has run it

DDD Review Skill

Review the codebase from a Domain-Driven Design perspective. Evaluate the structural health of domain modeling and identify areas for improvement.

Review Flow

Discover the domain: Read source code, directory structure, and documentation to understand the business domain and its boundaries.
Evaluate DDD alignment: Assess the codebase against the following dimensions:
- Bounded Contexts: Are domain boundaries clearly defined? Is there proper separation between contexts?
- Aggregates: Are aggregate roots correctly identified? Are consistency boundaries appropriate?
- Entities & Value Objects: Are entities and value objects properly distinguished? Are value objects immutable?
- Domain Services: Is business logic placed in the right layer? Are domain services used appropriately (not as a dumping ground)?
- Repositories: Do repositories abstract persistence correctly? Are they defined per aggregate?
- Domain Events: Are important state changes captured as domain events?
- Ubiquitous Language: Does the code reflect the business language consistently?
Identify issues: For each issue found, report:
- What: The specific DDD violation or weakness
- Where: File paths and code locations
- Why it matters: Impact on maintainability, correctness, or team communication
- Suggestion: Concrete steps to improve

Output format:

## DDD Review: <project or module name>

### Summary
<Brief overall assessment — 2-3 sentences>

### Scores
| Dimension              | Score (1-5) | Notes                  |
|------------------------|-------------|------------------------|
| Bounded Contexts       | ...         | ...                    |
| Aggregates             | ...         | ...                    |
| Entities & Value Objects| ...        | ...                    |
| Domain Services        | ...         | ...                    |
| Repositories           | ...         | ...                    |
| Domain Events          | ...         | ...                    |
| Ubiquitous Language    | ...         | ...                    |

### Issues

#### 1. <Issue title>
- **What**: ...
- **Where**: ...
- **Why it matters**: ...
- **Suggestion**: ...

### Strengths
- <What the codebase does well from a DDD perspective>

Guidelines