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
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.md — if missing, ERROR with Run: /iikit-00-constitutionIn addition to basic loading:
Extract enforcement rules — build checklist from normative statements:
CONSTITUTION ENFORCEMENT RULES:
[MUST] Use TDD - write tests before implementation
[MUST NOT] Use external dependencies without justificationDeclare hard gate:
CONSTITUTION GATE ACTIVE
Extracted X enforcement rules
ANY violation will HALT with explanationBefore writing ANY file: validate output against each principle. On violation: STOP, state the violated principle, explain what specifically violates it, suggest compliant alternative.
Constitution is recommended but not required for specify:
/iikit-00-constitution, then proceedInstall with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kit@2.3.5rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-clarify
iikit-03-plan
iikit-04-checklist
scripts
dashboard
iikit-05-testify
iikit-06-tasks
iikit-07-analyze
iikit-08-implement
iikit-09-taskstoissues
iikit-bugfix
scripts
iikit-core
scripts
bash
dashboard
powershell