CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/intent-integrity-kit

Closing the intent-to-code chasm - specification-driven development with BDD verification chain

86

1.82x
Quality

92%

Does it follow best practices?

Impact

86%

1.82x

Average score across 14 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
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-04-testify before /iikit-05-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

README.md

tile.json