Intent Integrity Kit Testify

Generate executable Gherkin .feature files from requirement artifacts before implementation. Enables TDD by creating hash-locked BDD scenarios that serve as acceptance criteria.

User Input

$ARGUMENTS

This skill accepts no user input parameters — it reads artifacts automatically.

Constitution Loading

Load constitution per constitution-loading.md (basic mode), then perform TDD assessment:

Scan for TDD indicators:

• Strong (MUST/REQUIRED + "TDD", "test-first", "red-green-refactor") -> mandatory
• Moderate (MUST + "test-driven", "tests before code") -> mandatory
• Implicit (SHOULD + "quality gates", "coverage requirements") -> optional
• Prohibition (MUST + "test-after", "no unit tests") -> forbidden (ERROR, halt)
• None found -> optional

Report per formatting-guide.md (TDD Assessment section).

Prerequisites Check

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

2. Parse for FEATURE_DIR and AVAILABLE_DOCS. Require plan.md and spec.md (ERROR if missing).

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-testify/scripts/bash/set-active-feature.sh --json <selection>

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

   Then re-run the prerequisites check from step 1.

4. Checklist gate per checklist-gate.md.

Acceptance Scenario Validation

Search spec.md for Given/When/Then patterns. If none found: ERROR with Run: /iikit-clarify.

Execution Flow

1. Load Artifacts

• Required: spec.md (acceptance scenarios), plan.md (API contracts, tech stack)
• Optional: data-model.md (validation rules)

2. Generate Gherkin Feature Files

Create .feature files in FEATURE_DIR/tests/features/:

Output directory: FEATURE_DIR/tests/features/ (create if it does not exist)

File organization: Generate one .feature file per user story or logical grouping. Use descriptive filenames (e.g., login.feature, user-management.feature).

2.1 Gherkin Tag Conventions

Every scenario MUST include traceability tags:

• @TS-XXX — test spec ID (sequential, unique across all .feature files)
• @FR-XXX — functional requirement from spec.md
• @SC-XXX — success criteria from spec.md
• @US-XXX — user story reference
• @P1 / @P2 / @P3 — priority level
• @acceptance / @contract / @validation — test type

SC-XXX coverage rule: For each SC-XXX in spec.md, ensure at least one scenario is tagged with the corresponding @SC-XXX. If an FR scenario already covers the success criterion, add the @SC-XXX tag to that scenario rather than creating a duplicate.

Feature-level tags for shared metadata:

• @US-XXX on the Feature line for the parent user story

2.2 Transformation Rules

From spec.md — Acceptance Tests: For each Given/When/Then scenario, generate a Gherkin scenario.

Use testspec-template.md as the Gherkin file template. For transformation examples, advanced constructs (Background, Scenario Outline, Rule), and syntax validation rules, see gherkin-reference.md.

3. Add DO NOT MODIFY Markers

Add an HTML comment at the top of each .feature file:

# DO NOT MODIFY SCENARIOS
# These .feature files define expected behavior derived from requirements.
# During implementation:
#   - Write step definitions to match these scenarios
#   - Fix code to pass tests, don't modify .feature files
#   - If requirements change, re-run /iikit-04-testify

4. Idempotency

If tests/features/ already contains .feature files:

• Preserve existing scenario tags (TS-XXX) where the source scenario is unchanged
• Add new scenarios for new requirements
• Mark removed scenarios as deprecated (comment out with # DEPRECATED:)
• Show diff summary of changes

5. Store Assertion Integrity Hash

CRITICAL: Store SHA256 hash of assertion content in both locations:

# Context.json (auto-derived from features directory path)
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/bash/testify-tdd.sh store-hash "FEATURE_DIR/tests/features"

# Git note (tamper-resistant backup — uses first .feature file for note attachment)
bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/bash/testify-tdd.sh store-git-note "FEATURE_DIR/tests/features"

Windows (PowerShell):

pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/powershell/testify-tdd.ps1 store-hash "FEATURE_DIR/tests/features"
pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/powershell/testify-tdd.ps1 store-git-note "FEATURE_DIR/tests/features"

The implement skill verifies this hash before proceeding, blocking if .feature file assertions were tampered with.

6. Report

Output: TDD determination, scenario counts by source (acceptance/contract/validation), output directory path, number of .feature files generated, hash status (LOCKED).

Error Handling

Dashboard Refresh

Regenerate the dashboard so the pipeline reflects the new testify artifacts:

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

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

Next Steps

Run: bash .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/bash/next-step.sh --phase 04 --json Windows: pwsh .tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify/scripts/powershell/next-step.ps1 -Phase 04 -Json

Parse the JSON and present:

1. If clear_after is true: suggest /clear before proceeding
2. Present next_step as the primary recommendation
3. If alt_steps non-empty: list as alternatives
4. For next_step and each alt_step, include the model_tier from the JSON so the user knows which model is best for each option. Look up tiers in model-recommendations.md for agent-specific switch commands.
5. Append dashboard link

Format:

Feature files generated!
Next: [/clear → ] <next_step> (model: <tier>)
[- <alt_step> — <reason> (model: <tier>)]

- Dashboard: file://$(pwd)/.specify/dashboard.html (resolve the path)