Closing the intent-to-code chasm - specification-driven development with BDD verification chain
95
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-04-testify before /iikit-05-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.7.12rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-plan
iikit-03-checklist
scripts
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