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

assertion-integrity.mdrules/

alwaysApply:
Yes

Assertion Integrity

  • NEVER modify .feature files or test-specs.md directly — run /iikit-04-testify to regenerate them
  • NEVER modify test assertions to make failing tests pass — fix the production code instead
  • NEVER delete or overwrite context.json assertion hashes — they are the integrity anchor
  • If a pre-commit hook blocks your commit for hash mismatch, do NOT use --no-verify — re-run /iikit-04-testify

rules

assertion-integrity.md

constitution.md

dashboard-refresh.md

phase-discipline.md

phase-separation.md

README.md

tile.json