Intent Integrity Kit Core

Core skill providing project initialization, status checking, and workflow help. [EXPLICIT]

User Input

$ARGUMENTS

Parse the user input to determine which subcommand to execute. [EXPLICIT]

Subcommands

1. init - Initialize intent-integrity-kit in a new or existing project
2. status - Show current project and feature status
3. use - Select the active feature for multi-feature projects
4. help - Display workflow phases and command reference

If no subcommand is provided, show help. [EXPLICIT]

Subcommand: 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. [EXPLICIT]

Argument Parsing

The $ARGUMENTS after init may include an optional path or URL to a PRD/SDD document (e.g., /iikit-core init ./docs/prd.md or /iikit-core init https://example.com/prd.md). If present, store it as prd_source for use in Step 6. [EXPLICIT]

Execution Flow

Working directory: All script paths below are relative to the project root. Before running any script, verify you are in the project root directory (pwd should show the directory containing tessl.json or .tessl/). If the script path doesn't resolve, find it: find . -path "*/iikit-core/scripts/bash/git-setup.sh" 2>/dev/null || find ~/.tessl -path "*/iikit-core/scripts/bash/git-setup.sh" 2>/dev/null

Step 0 — Detect environment

bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/git-setup.sh --json
# Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/git-setup.ps1 -Json

JSON fields: git_available, is_git_repo, has_remote, remote_url, is_github_remote, gh_available, gh_authenticated, has_iikit_artifacts. [EXPLICIT]

If gh_available is false, suggest: "GitHub CLI (gh) is not installed. Install it from https://cli.github.com/ for the best experience. Proceeding with curl fallback for GitHub operations." [EXPLICIT]

Step 1 — Git/GitHub setup

Auto-skip: If is_git_repo + has_remote, skip to Step 2.

Option	Requires	Action
A) Init here	git_available	git init, then offer GitHub repo create (gh or API). Ask public/private.
B) Clone	git_available	Ask for URL/owner/name. gh repo clone or git clone.
C) Skip	—	Proceed without git. Warn: no assertion integrity hooks.

Hide options whose prerequisites aren't met. If git_available is false, only C is available. [EXPLICIT]

Step 2 — Check if already initialized

test -f "CONSTITUTION.md"

Step 3 — Create directory structure

mkdir -p .specify specs

Step 4 — Initialize hooks

bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/init-project.sh --json
# Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/init-project.ps1 -Json

Installs pre-commit (assertion validation) and post-commit (hash storage) hooks. [EXPLICIT]

If git_user_configured is false: ask the user for their name and email, then run: [EXPLICIT]

git config user.name "<name>"
git config user.email "<email>"

Do NOT guess from hostname or system username. [EXPLICIT]

Step 5 — Create PREMISE.md

If PREMISE.md does not exist, create it from the user's input using premise-template.md. Extract from the user's init description: [EXPLICIT]

• 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. [EXPLICIT]

After writing PREMISE.md, validate: [EXPLICIT]

bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/validate-premise.sh --json "$PROJECT_PATH"

If validation fails (remaining placeholders or missing sections), fix and re-validate. [EXPLICIT]

Step 6 — Report

Directories created, hook status, PREMISE.md status. Suggest /iikit-00-constitution. [EXPLICIT]

Step 7 — Seed backlog from PRD (optional)

Gate: Requires 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. [EXPLICIT]

If Already Initialized

Show constitution status, feature count, and suggest /iikit-core status. [EXPLICIT]

Subcommand: status

Execution Flow

1. Run:

   bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/check-prerequisites.sh --phase status --json
   # Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/check-prerequisites.ps1 -Phase status -Json
   

2. 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.

Subcommand: use

Select the active feature when multiple features exist in specs/. [EXPLICIT]

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). [EXPLICIT]

Execution Flow

1. Run:

   bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/set-active-feature.sh --json <selector>
   # Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/set-active-feature.ps1 -Json <selector>
   

   Parse JSON for active_feature and stage.

2. 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. [EXPLICIT]

Subcommand: help (also default when no subcommand)

Display the workflow reference from help-reference.md verbatim. [EXPLICIT]

Resources

• spec-template.md, plan-template.md, agent-file-template.md — feature scaffolding
• prd-issue-template.md — PRD backlog seeding
• help-reference.md — workflow command reference

Error Handling

Unknown subcommand → show help. Not in a project → suggest init. Git unavailable → warn but continue. [EXPLICIT]

Usage

Example invocations: [EXPLICIT]

• "/iikit-core" — Run the full iikit core workflow
• "iikit core on this project" — Apply to current context

Validation Gate

• Output follows the defined structure and format [EXPLICIT]
• All claims are tagged with evidence markers [EXPLICIT]
• No placeholder content (TBD, TODO) [EXPLICIT]
• Actionable recommendations with priority levels [EXPLICIT]
• Assumptions explicitly documented [EXPLICIT]

Assumptions & Limits

• Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
• Requires English-language output unless otherwise specified [EXPLICIT]
• Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate