Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
Does it follow best practices?
Validation for skill structure
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 key criteria. It provides specific concrete outputs (user stories, Given/When/Then scenarios, FR-XXX requirements), uses natural trigger terms that product managers would actually say, and includes an explicit 'Use when...' clause with multiple relevant scenarios. The description is concise yet comprehensive.
| 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 terms product managers and developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on feature specification and product requirements documentation. The specific outputs (Given/When/Then, FR-XXX format) and triggers (PRD, acceptance criteria) create a distinct identity 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-crafted skill with excellent workflow clarity and progressive disclosure. The actionability is strong with executable commands and concrete examples throughout. Minor verbosity in platform-specific command repetition and the bug-fix detection section could be tightened, but overall the skill is production-ready and follows best practices.
| 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). Could be tightened by consolidating platform-specific commands into a reference. | 2 / 3 |
Actionability | Provides fully executable bash/PowerShell commands with specific flags, clear step-by-step workflow, concrete examples for branch naming, and explicit file paths. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Excellent multi-step sequencing with numbered phases (0-7), explicit validation step (Phase 4), feedback loop for clarifications (Phase 6), and clear decision points with user confirmation gates. 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) that are one level deep and clearly signaled with descriptive context. | 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.