Closing the intent-to-code chasm - specification-driven development with BDD verification chain
86
92%
Does it follow best practices?
Impact
86%
1.82xAverage score across 14 eval scenarios
Advisory
Suggest reviewing before use
spec.md, plan.md, and tasks.md in place/iikit-* skill validates its own prerequisites; if it blocks, run the prerequisite phase firstCONSTITUTION.md mandates TDD, ALWAYS run /iikit-04-testify before /iikit-05-tasks — tasks must reference test spec IDs.feature files exist for a feature, ALWAYS ensure step definitions and a BDD runner dependency are present before committing code/iikit-core status to check what's done and what's nextevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
rules
skills
iikit-00-constitution
scripts
dashboard
iikit-01-specify
iikit-02-plan
iikit-03-checklist
scripts
bash
dashboard
iikit-04-testify
iikit-05-tasks
iikit-06-analyze
iikit-07-implement
iikit-08-taskstoissues
iikit-bugfix
scripts
dashboard
iikit-clarify
iikit-core
references
scripts
bash
dashboard
powershell
templates