Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
Does it follow best practices?
Validation for skill structure
iikit-04-testify
skills/iikit-04-testify/SKILL.md
Discovery
100%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 is an excellent skill description that excels across all dimensions. It provides specific concrete actions (Gherkin generation, hash computation, criteria locking), includes comprehensive natural trigger terms that developers would actually use, explicitly states both capabilities and usage conditions, and carves out a distinct niche in the BDD/TDD space that won't conflict with general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate Gherkin .feature files', 'produces executable BDD scenarios with traceability tags', 'computes assertion integrity hashes', and 'locks acceptance criteria'. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (generate Gherkin files, produce BDD scenarios, compute hashes, lock criteria) AND when with explicit 'Use when...' clause listing five specific trigger scenarios including TDD, spec-based test creation, and red-green-refactor workflows. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'TDD', 'writing tests first', 'test cases from a spec', 'acceptance criteria', 'red-green-refactor', 'Gherkin', '.feature files', 'BDD scenarios'. These match how developers naturally discuss test-driven development. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Gherkin/.feature files, BDD scenarios, assertion integrity hashes, and TDD-specific terminology create a unique fingerprint unlikely to conflict with general testing or documentation skills. | 3 / 3 |
Total | 12 / 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 skill with excellent workflow clarity and actionability. The multi-step process is clearly sequenced with validation checkpoints, error handling is comprehensive, and all commands are executable. Minor verbosity from duplicating Windows commands and detailed tag documentation slightly impacts conciseness, but the content is otherwise lean and purposeful.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating Windows equivalents for every command, verbose tag documentation). The content assumes Claude's competence in most areas but could be tightened in places like the tag conventions section. | 2 / 3 |
Actionability | Provides fully executable bash/PowerShell commands, specific file paths, concrete Gherkin tag formats, and clear transformation rules. Commands are copy-paste ready with explicit paths and flags. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with numbered phases, explicit validation checkpoints (prerequisites check, checklist gate, acceptance scenario validation), clear error handling table, and hash verification as a blocking gate. The idempotency section handles edge cases well. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview sections and appropriate references to external files (constitution-loading.md, gherkin-reference.md, testspec-template.md). References are one level deep and clearly signaled with descriptive link text. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.