tessl-labs/intent-integrity-kit
Closing the intent-to-code chasm - specification-driven development with BDD verification chain
94
Quality
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
iikit-07-implement
skills/iikit-07-implement/SKILL.md
Discovery
92%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 a strong skill description that clearly articulates specific capabilities and provides explicit trigger conditions. The description uses proper third-person voice and covers both the 'what' and 'when' effectively. The main weakness is potential overlap with other coding-related skills, though the specific references to tasks.md and constitutional principles provide some differentiation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'coding each task', 'writes source files', 'runs tests', 'verifies assertion integrity', and 'validates output against constitutional principles'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Execute the implementation plan by coding each task...writes source files, runs tests, verifies assertion integrity') AND when ('Use when ready to build the feature, start coding, develop from the task list, or resume a partially completed implementation'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'build the feature', 'start coding', 'develop from the task list', 'resume a partially completed implementation'. Also references 'tasks.md' which is a specific artifact trigger. | 3 / 3 |
Distinctiveness Conflict Risk | While it references specific artifacts like 'tasks.md' and 'constitutional principles', terms like 'coding', 'build the feature', and 'start coding' could overlap with general coding assistance skills. The reference to implementation plans helps but isn't fully distinctive. | 2 / 3 |
Total | 11 / 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 high-quality, complex implementation skill with excellent workflow clarity and actionability. The BDD verification chain, parallel execution strategy, and validation gates are well-documented with concrete commands. Minor verbosity in script paths and some repeated patterns slightly reduce token efficiency, but the complexity of the workflow justifies most of the length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated script paths, verbose section headers). Some sections could be tightened, though most content is necessary for the complex workflow. | 2 / 3 |
Actionability | Provides fully executable bash commands with specific flags, clear script paths, and concrete examples. Every step has copy-paste ready commands with explicit parameters and expected outputs. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with explicit validation gates (§2.1-2.4), clear phase progression, failure handling (§6.5), and mandatory checkpoints before task completion. The BDD verification chain is particularly well-structured with RED/GREEN phases. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section hierarchy and appropriate references to external files (constitution-loading.md, parallel-execution.md, formatting-guide.md, etc.). References are one level deep and clearly signaled with bracketed links. | 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.