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
Last updated: [DATE]
This project uses specification-driven development with Intent Integrity Kit skills.
The development workflow follows these phases:
/iikit-constitution - Define project governance principles/iikit-specify - Create feature specification from natural language/iikit-clarify - Resolve ambiguities until spec is clear/iikit-plan - Create technical implementation plan/iikit-checklist - Generate domain-specific quality checklists/iikit-tasks - Generate task breakdown/iikit-analyze - Validate cross-artifact consistency/iikit-implement - Execute implementationNever skip phases. Each skill validates its prerequisites.
Read CONSTITUTION.md for this project's governing principles.
[EXTRACTED FROM ALL PLAN.MD FILES]
[ACTUAL STRUCTURE FROM PLANS][ONLY COMMANDS FOR ACTIVE TECHNOLOGIES][LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
[LAST 3 FEATURES AND WHAT THEY ADDED]
<!-- IIKIT-TECH-START --> <!-- Tech stack will be inserted here by /iikit-plan --> <!-- IIKIT-TECH-END -->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