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-01-specify
skills/iikit-01-specify/SKILL.md
Activation
100%This is an excellent skill description that hits all the marks. It provides specific concrete outputs (user stories, Given/When/Then scenarios, FR-XXX requirements), includes natural trigger terms users would actually say, explicitly states both what it does and when to use it, and carves out a distinct niche in feature/requirements specification that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist' - these are precise, actionable outputs. | 3 / 3 |
Completeness | Clearly answers both what ('generates user stories with Given/When/Then scenarios, functional requirements, success criteria, quality checklist') AND when ('Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'feature', 'PRD', 'user stories', 'acceptance criteria', 'requirements', 'product idea' - these are all common phrases users naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on feature specification and requirements documentation with distinct triggers like 'PRD', 'Given/When/Then', 'FR-XXX', 'acceptance criteria' - unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%This is a well-structured skill with strong actionability and workflow clarity. The multi-step process is clearly sequenced with validation checkpoints, and external references are appropriately organized. Minor verbosity in the bug-fix detection section and command duplication for cross-platform support slightly reduce token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating Unix/Windows commands, verbose bug-fix detection explanation). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides concrete, executable bash/PowerShell commands with specific flags, clear file paths, and explicit step-by-step instructions. The branch naming examples and script invocations are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear numbered sequence (Steps 0-7) with explicit validation checkpoint (Step 4 Phase Separation Validation with auto-fix and re-validate loop). Includes decision points for bug-fix detection and branch creation with clear branching logic. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to external files (constitution-loading.md, spec-template.md, phase-separation-rules.md, formatting-guide.md, model-recommendations.md). References are one level deep and clearly signaled with purpose. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.