Intent Integrity Kit Checklist

Generate "Unit Tests for English" — checklists that validate REQUIREMENTS quality, not implementation.

Core Principle

Every checklist item evaluates the requirements themselves for completeness, clarity, consistency, measurability, and coverage. Items MUST NOT test implementation behavior.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Constitution Loading

Load constitution per constitution-loading.md (basic mode).

Prerequisites Check

1. Run: bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/bash/check-prerequisites.sh --phase 04 --json Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/powershell/check-prerequisites.ps1 -Phase 04 -Json

2. Parse JSON for FEATURE_DIR and AVAILABLE_DOCS.

3. If JSON contains needs_selection: true: present the features array as a numbered table (name and stage columns). Follow the options presentation pattern in conversation-guide.md. After user selects, run:

   bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/bash/set-active-feature.sh --json <selection>

   Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/powershell/set-active-feature.ps1 -Json <selection>

   Then re-run the prerequisites check from step 1.

Execution Steps

1. Clarify Intent

Derive up to THREE contextual questions (skip if unambiguous from $ARGUMENTS):

• Scope: include integration touchpoints?
• Risk: which areas need mandatory gating?
• Depth: lightweight sanity list or formal release gate?
• Audience: author-only or peer PR review?

2. Load Feature Context

Read from FEATURE_DIR: spec.md (required), plan.md (optional), tasks.md (optional).

3. Generate Checklist

Create FEATURE_DIR/checklists/[domain].md.

Item structure: question format about requirement quality, with quality dimension tag and spec reference.

Correct: "Are visual hierarchy requirements defined with measurable criteria?" [Clarity, Spec SFR-1] Wrong: "Verify the button clicks correctly" (this tests implementation)

Categories: Requirement Completeness, Clarity, Consistency, Acceptance Criteria Quality, Scenario Coverage, SC-XXX Test Coverage, Edge Case Coverage, Non-Functional Requirements, Dependencies & Assumptions.

Traceability: >=80% of items must reference spec sections or use markers: [Gap], [Ambiguity], [Conflict], [Assumption].

See checklist-examples.md for correct/wrong examples and required patterns.

Use checklist-template.md for format structure.

4. Gap Resolution (Interactive)

For each [Gap] item: follow the gap resolution pattern in conversation-guide.md. Present missing requirement, explain risk, offer options. On resolution: update spec.md and check item off. Skip if --no-interactive or no gaps.

5. Remaining Item Validation

After gap resolution, validate ALL unchecked [ ] items against spec/plan/constitution:

• If covered: check off with justification
• If genuine gap: convert to [Gap] and resolve or defer

Continue until all items are [x] or explicitly deferred.

IMPORTANT: Checklists are optional — not creating one is fine. But once created, they MUST reach 100% before the skill reports success.

6. Report

Output: checklist path, item counts (total/checked/deferred), gap resolution summary, completion percentage.

Next Steps

Dashboard Refresh

Regenerate the dashboard so the pipeline reflects checklist completion:

bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/bash/generate-dashboard-safe.sh

Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-checklist/scripts/powershell/generate-dashboard-safe.ps1

Next Steps

Suggest the user run /clear before proceeding — the interactive gap resolution consumed significant context. State is preserved in checklist files and .specify/context.json.

Check the constitution's TDD policy (run bash .tessl/.../testify-tdd.sh get-tdd-determination CONSTITUTION.md):

If TDD mandatory:

Checklist complete! (100%)
Next steps:
- /iikit-05-testify - (REQUIRED by constitution) Generate test specifications
- /iikit-06-tasks - Generate task breakdown from plan
- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)

If TDD optional or no TDD policy:

Checklist complete! (100%)
Next steps:
- /iikit-05-testify - (Optional) Generate test specifications for TDD
- /iikit-06-tasks - Generate task breakdown from plan
- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)

If deferred items remain, warn that downstream skills will flag incomplete checklists.

You MUST read model-recommendations.md, check the expiration date (refresh via web search if expired), detect the agent via env vars, and include a model switch tip in the output above if the next phase needs a different model tier. Add Tip: <suggestion> as the last line inside the code block.