Content
50%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured but overly abstract guide to DDD strategic design. Its main weakness is lack of actionability — it tells Claude what to produce (subdomain tables, glossaries) without showing concrete examples of those artifacts. The referenced template file doesn't exist in the bundle, undermining progressive disclosure.
Suggestions
Add a concrete example of at least one output artifact (e.g., a sample subdomain classification table with 2-3 rows) so Claude knows the expected format and level of detail.
Include a sample glossary entry showing canonical term, definition, anti-terms, and owning bounded context to make the glossary instruction actionable.
Either provide the referenced `references/strategic-design-template.md` file in the bundle or inline the essential template structure directly in the skill.
Add a validation step such as 'Review context boundaries with domain experts before capturing in ADRs' to strengthen the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly lean and doesn't over-explain DDD concepts Claude already knows. The 'Use this skill when' and 'Do not use this skill when' sections are useful but slightly verbose — the negative cases could be trimmed. Overall efficient with minor padding. | 4 / 5 |
Actionability | The instructions are high-level directives ('Extract domain capabilities and classify subdomains') without concrete examples of what the output should look like. No example subdomain classification table, no sample glossary entry, no template structure is shown inline. The 'Examples' section only shows a prompt, not an expected output. | 2 / 5 |
Workflow Clarity | There is a 4-step sequence that provides a logical ordering, but steps lack specificity and there are no validation checkpoints or feedback loops. For a non-destructive instruction-only skill this is acceptable but still missing verification steps (e.g., 'validate context boundaries with stakeholders before finalizing'). | 3 / 5 |
Progressive Disclosure | The skill references `references/strategic-design-template.md` for detailed templates, which is good progressive disclosure in principle. However, no bundle files exist to back this reference, and the required artifacts section could benefit from linking to example templates or schemas. The structure is reasonable but the dangling reference is a problem. | 3 / 5 |
Total | 12 / 20 Passed |