Closing the intent-to-code chasm - specification-driven development with BDD verification chain
94
92%
Does it follow best practices?
Impact
95%
1.82xAverage score across 14 eval scenarios
Advisory
Suggest reviewing before use
[PRINCIPLE_1_DESCRIPTION]
[PRINCIPLE_2_DESCRIPTION]
[PRINCIPLE_3_DESCRIPTION]
[PRINCIPLE_4_DESCRIPTION]
[PRINCIPLE_5_DESCRIPTION]
[SECTION_2_CONTENT]
[SECTION_3_CONTENT]
Pre-commit hooks are a critical integrity gate. The following are prohibited:
git commit --no-verify or git commit -n to bypass hooks.git/hooks/git commit-tree, git mktree) to circumvent hooks/iikit-04-testify to regenerate hashesCI enforcement recommended: Add verify-assertion-integrity.sh to your CI pipeline for server-side verification that cannot be bypassed. See the CI integration reference for setup instructions.
[GOVERNANCE_RULES]
Version: [CONSTITUTION_VERSION] | Ratified: [RATIFICATION_DATE] | Last Amended: [LAST_AMENDED_DATE]
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
scripts
bash
dashboard
powershell
templates