CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/intent-integrity-kit

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

94

1.82x
Quality

92%

Does it follow best practices?

Impact

95%

1.82x

Average score across 14 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

constitution-template.mdskills/iikit-00-constitution/templates/

[PROJECT_NAME] Constitution

Core Principles

I. [PRINCIPLE_1_NAME]

[PRINCIPLE_1_DESCRIPTION]

II. [PRINCIPLE_2_NAME]

[PRINCIPLE_2_DESCRIPTION]

III. [PRINCIPLE_3_NAME]

[PRINCIPLE_3_DESCRIPTION]

IV. [PRINCIPLE_4_NAME]

[PRINCIPLE_4_DESCRIPTION]

V. [PRINCIPLE_5_NAME]

[PRINCIPLE_5_DESCRIPTION]

[SECTION_2_NAME]

[SECTION_2_CONTENT]

[SECTION_3_NAME]

[SECTION_3_CONTENT]

Integrity

Pre-Commit Hook Enforcement (NON-NEGOTIABLE)

Pre-commit hooks are a critical integrity gate. The following are prohibited:

  • NEVER use git commit --no-verify or git commit -n to bypass hooks
  • NEVER delete, modify, or disable files in .git/hooks/
  • NEVER use git plumbing commands (git commit-tree, git mktree) to circumvent hooks
  • If a pre-commit hook blocks your commit, fix the root cause — do not work around the hook
  • For assertion integrity failures: re-run /iikit-04-testify to regenerate hashes

CI enforcement recommended: Add verify-assertion-integrity.sh to your CI pipeline for server-side verification that cannot be bypassed. See the CI integration reference for setup instructions.

Governance

[GOVERNANCE_RULES]

Version: [CONSTITUTION_VERSION] | Ratified: [RATIFICATION_DATE] | Last Amended: [LAST_AMENDED_DATE]

skills

README.md

tile.json