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-08-implement
skills/iikit-08-implement/SKILL.md
Activation
100%This is a strong skill description that clearly articulates specific capabilities (writing source files, running tests, verifying assertions) and provides explicit trigger conditions for when to use it. The description uses proper third-person voice and includes natural language triggers that users would actually say when ready to implement code from a task list.
| 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 | Has a clear niche focused on executing from tasks.md with specific triggers like 'implementation plan', 'task list', and 'resume a partially completed implementation'. The reference to 'constitutional principles' and 'assertion integrity' further distinguishes it from generic coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%This is a high-quality, complex implementation skill with excellent workflow clarity and actionability. The multi-phase execution flow with explicit validation gates, TDD enforcement, and error handling demonstrates sophisticated design. Minor verbosity in some sections (repeated Windows notes, detailed TDD explanations) slightly impacts token efficiency but doesn't significantly detract from overall quality.
Suggestions
Consider consolidating the Windows PowerShell note into a single reference section rather than repeating inline, to reduce token overhead.
The TDD phases (RED/GREEN) explanation could be shortened since Claude understands TDD concepts—focus on the specific verification commands rather than explaining the methodology.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated script paths, verbose explanations of TDD phases). Some sections could be tightened, though most content is necessary for the complex workflow. | 2 / 3 |
Actionability | Provides fully executable bash/PowerShell commands, specific script paths, concrete commit message formats, and exact JSON parsing expectations. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with explicit validation gates (§2.1-2.4), numbered phases, clear checkpoints, and a comprehensive error handling table. Feedback loops are explicit (RED->GREEN, verify->fix->retry). | 3 / 3 |
Progressive Disclosure | Well-structured with clear section headers and appropriate references to external files (constitution-loading.md, parallel-execution.md, tessl-integration.md, etc.). References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.