What problem does it solve? Teams practicing TDD often write acceptance criteria in specs but never convert them into executable tests before coding, letting requirements drift during implementation. This Skill transforms spec.md acceptance scenarios into Gherkin .feature files with traceability tags and locks them with a SHA256 integrity hash so tests cannot be silently modified. ## Core Features & Use Cases - Gherkin Generation from Specs: Converts Given/When/Then acceptance scenarios, API contracts from plan.md, and validation rules from data-model.md into organized .feature files with @TS/@FR/@SC/@US traceability tags. - Assertion Integrity Locking: Computes a SHA256 hash of generated scenarios, stores it in context.json and a git note, and lets the implement phase verify tests were not altered. - TDD Assessment & Gating: Scans the project constitution for TDD indicators (mandatory, optional, or forbidden) and halts with an error if test-after development is mandated. - Use Case: After running /iikit-02-plan for a login feature, invoke this Skill to produce login.feature with acceptance, contract, and validation scenarios before any implementation code is written. ## Quick Start Run the testify phase to generate Gherkin feature files from my current spec.md and plan.md, then lock the scenarios with an integrity hash.
