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
spec.md, plan.md, and tasks.md in place/iikit-* skill validates its own prerequisites; if it blocks, run the prerequisite phase firstCONSTITUTION.md mandates TDD, ALWAYS run /iikit-05-testify before /iikit-06-tasks — tasks must reference test spec IDs.feature files exist for a feature, ALWAYS ensure step definitions and a BDD runner dependency are present before committing code/iikit-core status to check what's done and what's nextInstall 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