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-separation.mdrules/

alwaysApply:
Yes

Phase Separation

  • NEVER put technology choices (languages, frameworks, databases, libraries) in CONSTITUTION.md — those belong in plan.md
  • NEVER put implementation details (schemas, APIs, file structures, architecture) in spec.md — those belong in plan.md
  • NEVER put governance principles (project-wide rules, team process, non-negotiable standards) in plan.md — those belong in CONSTITUTION.md
  • If you spot a violation, rewrite the content for the correct artifact rather than leaving it in the wrong place

README.md

tile.json