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

agent-file-template.mdskills/iikit-03-plan/templates/

[PROJECT NAME] Development Guide

Last updated: [DATE]

Overview

This project uses specification-driven development with Intent Integrity Kit skills.

Workflow

The development workflow follows these phases:

  1. /iikit-constitution - Define project governance principles
  2. /iikit-specify - Create feature specification from natural language
  3. /iikit-clarify - Resolve ambiguities until spec is clear
  4. /iikit-plan - Create technical implementation plan
  5. /iikit-checklist - Generate domain-specific quality checklists
  6. /iikit-tasks - Generate task breakdown
  7. /iikit-analyze - Validate cross-artifact consistency
  8. /iikit-implement - Execute implementation

Never skip phases. Each skill validates its prerequisites.

Constitution

Read CONSTITUTION.md for this project's governing principles.

Active Technologies

[EXTRACTED FROM ALL PLAN.MD FILES]

Project Structure

[ACTUAL STRUCTURE FROM PLANS]

Commands

[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]

Conventions

[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]

Recent Changes

[LAST 3 FEATURES AND WHAT THEY ADDED]

<!-- IIKIT-TECH-START --> <!-- Tech stack will be inserted here by /iikit-plan --> <!-- IIKIT-TECH-END -->

Install with Tessl CLI

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

skills

README.md

tile.json