Initialize an IIKit project, check feature progress, select the active feature, and display the workflow command reference. Use when starting a new project, running init, checking status, switching between features, or looking up available commands and phases.
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill uses the workspace's default tool permissions.
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/ambiguity-taxonomies.mdreferences/checklist-gate.mdreferences/constitution-loading.mdreferences/conversation-guide.mdreferences/formatting-guide.mdreferences/help-reference.mdreferences/model-recommendations.mdreferences/phase-separation-rules.mdreferences/prd-seeding.mdCore skill providing project initialization, status checking, and workflow help. [EXPLICIT]
$ARGUMENTS
Parse the user input to determine which subcommand to execute. [EXPLICIT]
If no subcommand is provided, show help. [EXPLICIT]
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]
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]
Working directory: All script paths below are relative to the project root. Before running any script, verify you are in the project root directory (
pwdshould show the directory containingtessl.jsonor.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
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]
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]
test -f "CONSTITUTION.md"
mkdir -p .specify specs
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]
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]
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]
Directories created, hook status, PREMISE.md status. Suggest /iikit-00-constitution. [EXPLICIT]
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]
Show constitution status, feature count, and suggest /iikit-core status. [EXPLICIT]
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
Present results (all logic is in script output — just display):
feature_stage, artifact status (artifacts object), checklist progress (checklist_checked/checklist_total), ready_for phase, next_stepclear_before is true, prepend /clear suggestion. If next_step is null, report feature as complete.Select the active feature when multiple features exist in specs/. [EXPLICIT]
The $ARGUMENTS after use is the feature selector: a number (1, 001), partial name (user-auth), or full directory name (001-user-auth). [EXPLICIT]
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.
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]
Display the workflow reference from help-reference.md verbatim. [EXPLICIT]
Unknown subcommand → show help. Not in a project → suggest init. Git unavailable → warn but continue. [EXPLICIT]
Example invocations: [EXPLICIT]
| 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 |
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.