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
[PROJECT_DESCRIPTION]
<!-- One paragraph: what is this application/system? What does it do? -->[TARGET_USERS]
<!-- Target users, personas, or audiences. Who benefits from this? -->[PROBLEM_AND_VALUE]
<!-- The problem being solved and the value proposition. Why does this need to exist? -->[DOMAIN_AND_TERMINOLOGY]
<!-- Business or technical domain. Key terms and their definitions. Industry context. -->[SYSTEM_BOUNDARIES]
<!-- High-level system boundaries and major components. What's in, what's out. -->evals
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