iikit-05-testify

Test-spec generation converts your requirement artifacts—spec.md, plan.md, and data-model.md—into structured acceptance, contract, and validation tests before implementation begins. This enforces Test-Driven Development by locking requirements upfront and ensures tests guide your code, not the reverse.

Prepare spec.md (requirements), plan.md (design decisions), and data-model.md (data structures) in your feature directory. The skill analyzes these artifacts to derive test specifications, which are then stored in FEATURE_DIR/tests/test-specs.md for implementation.

Test specifications are linked to functional requirements, scenario contracts, and user stories through an integrity hash. This end-to-end traceability ensures acceptance criteria remain connected to source artifacts, enabling governance audits and stable delivery.

Yes. The skill generates acceptance tests (user-facing criteria), contract tests (service boundaries), and validation tests (data integrity) from a single requirements pass. All three test types are derived and stored together in your test-specs file.

Test specifications define acceptance criteria before implementation starts, creating a TDD contract: tests exist first, code follows. This prevents scope creep, aligns implementation with requirements, and ensures tests remain authoritative throughout development.