Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides clear, actionable guidance for creating technical design documents. The workflow is well-sequenced with appropriate references to shared conventions, and the design template gives concrete structure. The main weakness is moderate verbosity in the template section, though the 800-word budget rule helps constrain output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy — the design document format template is quite long and could be more compact. The mode-specific branching logic is repeated across steps. However, it mostly avoids explaining things Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, specific guidance: exact file paths, a complete markdown template for the design document, specific artifact keys, a structured return format, and clear rules. The steps are executable and copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit steps: load skills → read codebase → write design → persist artifact → return summary. Step 4 is marked as MANDATORY. Mode-specific branching is clearly documented at each step. The persistence step serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | The skill appropriately delegates shared concerns to `skills/_shared/sdd-phase-common.md` (Sections A-D) and `skills/_shared/openspec-convention.md`, keeping the main file focused on design-specific content. References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |