Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
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 -->Install with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kit@2.3.5rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-clarify
iikit-03-plan
iikit-04-checklist
scripts
dashboard
iikit-05-testify
iikit-06-tasks
iikit-07-analyze
iikit-08-implement
iikit-09-taskstoissues
iikit-bugfix
scripts
iikit-core
scripts
bash
dashboard
powershell