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-01-specify
skills/iikit-01-specify/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 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 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 detailed, concrete 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 PRD creation with distinct triggers like 'Given/When/Then', 'FR-XXX', 'PRD', 'acceptance criteria' - unlikely to conflict with general documentation or coding 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-structured, actionable skill with clear workflow sequencing and appropriate progressive disclosure through external references. The main weakness is some verbosity in the bug-fix detection section and repeated platform-specific command blocks that could potentially be consolidated. Overall, it provides excellent guidance for a complex multi-step specification workflow.
Suggestions
Consider consolidating the repeated Unix/Windows command patterns into a single reference or convention statement at the top, reducing duplication across sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating Unix/Windows commands in multiple sections, verbose bug-fix detection explanation). Some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides fully executable bash/PowerShell commands with specific flags, clear file paths, and concrete examples (branch naming transformations). The workflow is copy-paste ready with explicit script invocations. | 3 / 3 |
Workflow Clarity | Clear numbered sequence (0-7) with explicit validation steps (Phase Separation Validation, Spec Quality Checklist), feedback loops for clarifications, and conditional branching (bug-fix detection, branch creation). Includes re-validation until clean. | 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 relative paths. | 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.