sdd-apply
Implement tasks from the change, writing actual code following the specs and design. Trigger: "apply", "implement", "implementar", "code it", "build it", "sdd apply", "ejecutar tareas", "/sdd:apply".
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has strong trigger term coverage with both English and Spanish variants, and clearly separates the 'what' from the 'when' with an explicit Trigger clause. However, the capability description is somewhat vague ('writing actual code following the specs and design') and could benefit from more specific actions. The mix of distinctive SDD-specific triggers with generic coding terms creates moderate conflict risk.
Suggestions
Add more specific concrete actions like 'creates functions, modifies classes, updates tests based on SDD task specifications'
Clarify what 'the change' and 'specs and design' refer to (e.g., 'SDD change documents' or 'software design documents') to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (implementing tasks from change specs) and a general action (writing code), but lacks specific concrete actions like 'create functions', 'modify classes', or 'update tests'. | 2 / 3 |
Completeness | Clearly answers both what ('Implement tasks from the change, writing actual code following the specs and design') and when (explicit 'Trigger:' clause with multiple trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'apply', 'implement', 'code it', 'build it', plus Spanish variants ('implementar', 'ejecutar tareas') and command-style triggers ('/sdd:apply', 'sdd apply'). | 3 / 3 |
Distinctiveness Conflict Risk | The 'sdd apply' and '/sdd:apply' triggers are distinctive, but generic terms like 'implement', 'code it', 'build it' could overlap with general coding skills or other implementation-focused skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
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-crafted implementation skill with excellent workflow clarity and actionability. The TDD workflow is particularly well-defined with explicit RED/GREEN/REFACTOR steps and validation checkpoints. Minor verbosity in some sections (conflict resolution, error recovery) could be tightened, but the content is generally efficient and comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating mode resolution patterns that could reference shared files more briefly). The conflict resolution and error recovery tables are useful but could be more condensed. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, command patterns, markdown task syntax, and clear decision trees. The TDD workflow with exact test command patterns and the step-by-step implementation process are copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints (pre-implementation checklist, self-verify after each task, test pass/fail confirmation in TDD). Clear feedback loops for error recovery and explicit 'STOP and report' conditions. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections and references to shared files (`skills/_shared/persistence-contract.md`, `skills/_shared/engram-convention.md`). Content is appropriately organized with tables for quick reference and expandable detail where needed. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- Yoizen/dev-ai-workflow
- Commit
d9bf9a4
- Reviewed
Table of Contents
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.