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

constitution-loading.mdskills/iikit-01-specify/references/

Constitution & Premise Loading Procedure

Premise Loading (all skills)

Read PREMISE.md if it exists. This provides app-wide context: what the project is, who it's for, the domain, and the high-level vision. Use it to inform decisions across all phases — feature scoping, architectural choices, naming conventions, and priority judgments. If missing: proceed without it (not required, but strongly recommended).

Constitution Loading (most skills)

  1. Read CONSTITUTION.md — if missing, ERROR with Run: /iikit-00-constitution
  2. Parse all principles, constraints, and governance rules
  3. Note all MUST, MUST NOT, SHALL, REQUIRED, NON-NEGOTIABLE statements

Enforcement Mode (plan, implement)

In addition to basic loading:

  1. Extract enforcement rules — build checklist from normative statements:

    CONSTITUTION ENFORCEMENT RULES:
    [MUST] Use TDD - write tests before implementation
    [MUST NOT] Use external dependencies without justification
  2. Declare hard gate:

    CONSTITUTION GATE ACTIVE
    Extracted X enforcement rules
    ANY violation will HALT with explanation
  3. Before writing ANY file: validate output against each principle. On violation: STOP, state the violated principle, explain what specifically violates it, suggest compliant alternative.

Soft Loading (specify)

Constitution is recommended but not required for specify:

  • If missing: WARNING recommending /iikit-00-constitution, then proceed
  • If exists: parse and validate against principles

Install with Tessl CLI

npx tessl i tessl-labs/intent-integrity-kit@2.3.5

skills

README.md

tile.json