CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/intent-integrity-kit

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

Overview
Skills
Evals
Files

phase-discipline.mdrules/

alwaysApply:
Yes

Phase Discipline

  • NEVER write production code without spec.md, plan.md, and tasks.md in place
  • NEVER skip phases — each /iikit-* skill validates its own prerequisites; if it blocks, run the prerequisite phase first
  • When CONSTITUTION.md mandates TDD, ALWAYS run /iikit-05-testify before /iikit-06-tasks — tasks must reference test spec IDs
  • When .feature files exist for a feature, ALWAYS ensure step definitions and a BDD runner dependency are present before committing code
  • Use /iikit-core status to check what's done and what's next

Install with Tessl CLI

npx tessl i tessl-labs/intent-integrity-kit@2.3.5

rules

assertion-integrity.md

constitution.md

dashboard-refresh.md

phase-discipline.md

phase-separation.md

README.md

tile.json