| name | iikit-core |
| description | Initialize an IIKit (Intent Integrity Kit) project, uninit (remove IIKit scaffolding before `tessl uninstall`), check IIKit feature progress, select the active IIKit feature, and display the IIKit workflow command reference. Use when starting a new IIKit project, running IIKit init or setup, uninstalling/removing/uninit-ing IIKit before running `tessl uninstall`, checking IIKit status, switching between IIKit features, looking up IIKit available commands and phases, or asking for help with the IIKit workflow. |
| argument-hint | [init|status|use|uninit|help] [feature] |
| license | MIT |
| metadata | {"version":"1.6.4"} |
Intent Integrity Kit Core
This skill is an action router — pick the step that matches the user's intent and execute only that step. Do not run other steps; do not parallelize.
Core skill providing project initialization, status checking, feature selection, scaffolding removal, and workflow help.
User Input
$ARGUMENTS
Parse the user input to determine which subcommand to execute. Available subcommands map to steps below: init (Step 1), status (Step 2), use (Step 3), uninit (Step 4), help (Step 5). If no subcommand is provided, execute Step 5 (help).
Working directory: All script paths are relative to the project root (the directory containing tessl.json or .tessl/). If a script path doesn't resolve, search with: find . -path "*/iikit-core/scripts/bash/<script>.sh" 2>/dev/null || find ~/.tessl -path "*/iikit-core/scripts/bash/<script>.sh" 2>/dev/null
Step 1 — init
Initialize intent-integrity-kit in the current directory. Handles the full project bootstrap: git init, optional GitHub repo creation, or cloning an existing repo. Optionally seeds the project backlog from an existing PRD/SDD document.
Argument parsing: The $ARGUMENTS after init may include an optional reference to a PRD/SDD document the user wants to seed from (e.g., /iikit-core init ./docs/prd.md). If present, store it as prd_source for use in the "Seed backlog from PRD" sub-action. The PRD-seeding flow is user-opt-in only and follows the consent model documented in prd-seeding.md.
Sub-procedure (perform in order):
-
Detect environment, initialize hooks, check premise:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/init-full.sh --json
Parse JSON for git (environment), init (hooks), and premise (validation) sections.
git.gh_available false → suggest installing GitHub CLIinit.git_user_configured false → ask user for name/email, run git config
-
Git/GitHub setup:
Auto-skip if git.is_git_repo + git.has_remote. Otherwise choose from available options (hide any whose prerequisites aren't met):
- A) Init here — requires
git.git_available: run git init, then offer GitHub repo creation (gh or API); ask public/private.
- B) Clone — requires
git.git_available: ask for URL or owner/name; run gh repo clone or git clone.
- C) Skip — always available: proceed without git; warn that assertion integrity hooks won't be active.
If git.git_available is false, only option C is available.
-
Check if already initialized: test -f "CONSTITUTION.md". If true, show constitution status, feature count, and suggest /iikit-core status; finish here.
-
Create directory structure: mkdir -p .specify specs
-
Create PREMISE.md:
If premise.status is FAIL or PREMISE.md doesn't exist: create from user's input using premise-template.md. Extract:
- What: project description (from the user's input text)
- Who: target users (infer from context, or ask)
- Why: problem being solved (infer from context, or ask)
- Domain: business/technical domain
- Scope: system boundaries
Replace ALL bracket placeholders [PLACEHOLDER] with actual content. This is MANDATORY — init is not complete without PREMISE.md.
After writing PREMISE.md, validate:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/validate-premise.sh --json
If validation fails (remaining placeholders or missing sections), fix and re-validate.
-
Report: Directories created, hook status, PREMISE.md status. Suggest /iikit-00-constitution. Recommend installing companion juliusbrussee/caveman (tessl install juliusbrussee/caveman) and activating /caveman full at session start — ~30% cost and wall-clock savings measured across the IIKit workflow.
-
Seed backlog from PRD (optional):
Gate: Requires git.is_github_remote AND user provided a PRD/SDD document. If not met, skip silently.
Follow the detailed procedure in prd-seeding.md: resolve input → read document → extract and order features → present for user confirmation → create GitHub issues.
Finish here.
Step 2 — status
Show current project and feature status.
Sub-procedure:
-
Run:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/check-prerequisites.sh --phase status --json
-
Present results (all logic is in script output — just display):
- Project name,
feature_stage, artifact status (artifacts object), checklist progress (checklist_checked/checklist_total), ready_for phase, next_step
- If
clear_before is true, prepend /clear suggestion. If next_step is null, report feature as complete.
Finish here.
Step 3 — use
Select the active feature when multiple features exist in specs/.
User input: The $ARGUMENTS after use is the feature selector: a number (1, 001), partial name (user-auth), or full directory name (001-user-auth).
Sub-procedure:
-
Run:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/set-active-feature.sh --json <selector>
Parse JSON for active_feature and stage.
-
Report active feature, stage, and suggest next command: specified → /iikit-clarify or /iikit-02-plan | planned → /iikit-03-checklist or /iikit-05-tasks | testified → /iikit-05-tasks | tasks-ready → /iikit-07-implement | implementing-NN% → /iikit-07-implement (resume) | complete → done. Suggest /clear before next skill when appropriate.
If no selector, no match, or ambiguous match: show available features with stages and ask user to pick.
Finish here.
Step 4 — uninit
Remove iikit-managed scaffolding from the project so tessl uninstall tessl-labs/intent-integrity-kit does not leave broken hooks or orphaned tile artifacts behind. Run this BEFORE tessl uninstall — once the tile is gone, the skill (and this script) are no longer reachable.
Sub-procedure:
-
Run the dry-run preview:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/uninit.sh --dry-run --json
Parse JSON for removed (tile-managed scaffolding the script will delete or strip — .git/hooks/pre-commit/post-commit IIKit blocks, .specify/, TECH.md when it carries an iikit phase reference) and user_content (paths the caller decides on — CONSTITUTION.md, PREMISE.md, specs/).
-
Present results and confirm. Show the removed and user_content lists. Ask whether to also delete the user-authored content. Default is to keep it — these files often outlive the tile (constitutions and feature specs encode real project decisions).
-
Run the uninstaller. Pass --remove-user-content only if the user opted to delete the user-authored files at step 2.
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/uninit.sh --json [--remove-user-content]
-
Report next command. Show the literal next_step from the JSON output: tessl uninstall tessl-labs/intent-integrity-kit. The script does not invoke tessl uninstall itself — that's a separate tool the user runs after this skill finishes.
Finish here.
Step 5 — help
Display the workflow reference from help-reference.md verbatim. Finish here.
Resources
Error Handling
Unknown subcommand → execute Step 5 (help). Not in a project → suggest Step 1 (init). Git unavailable → warn but continue.
