tessl-labs/intent-integrity-kit
Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
iikit-05-testify
skills/iikit-05-testify/SKILL.md
Activation
100%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%This is a well-crafted skill with excellent workflow clarity and progressive disclosure. The actionability is strong with executable commands and specific file paths. The main weakness is moderate verbosity in some sections (tag conventions, TDD indicators) that could be tightened without losing clarity.
Suggestions
Condense the TDD indicators section into a compact table format rather than bullet points with explanations
Consider moving the detailed Gherkin tag conventions (section 2.1) to the referenced gherkin-reference.md to reduce inline content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what TDD indicators mean, verbose tag convention lists). The Windows command alternatives add necessary but repetitive content that could be structured more compactly. | 2 / 3 |
Actionability | Provides fully executable bash/PowerShell commands, specific file paths, concrete Gherkin tag conventions with examples, and clear transformation rules. Commands are copy-paste ready with actual script paths. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with numbered phases, explicit validation checkpoints (prerequisites check, acceptance scenario validation, hash storage), clear error handling table with specific responses, and idempotency handling for existing files. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to external files (constitution-loading.md, formatting-guide.md, gherkin-reference.md, testspec-template.md) that are one level deep and clearly signaled. Main content stays focused on the workflow while delegating details appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.