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-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

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