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
Read PREMISE.md if it exists. This provides app-wide context: what the project is, who it's for, the domain, and the high-level vision. Use it to inform decisions across all phases — feature scoping, architectural choices, naming conventions, and priority judgments. If missing: proceed without it (not required, but strongly recommended).
CONSTITUTION.md — if missing, ERROR with Run: /iikit-00-constitutionIn addition to basic loading:
Extract enforcement rules — build checklist from normative statements:
CONSTITUTION ENFORCEMENT RULES:
[MUST] Use TDD - write tests before implementation
[MUST NOT] Use external dependencies without justificationDeclare hard gate:
CONSTITUTION GATE ACTIVE
Extracted X enforcement rules
ANY violation will HALT with explanationBefore writing ANY file: validate output against each principle. On violation: STOP, state the violated principle, explain what specifically violates it, suggest compliant alternative.
Constitution is recommended but not required for specify:
/iikit-00-constitution, then proceedevals
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