skills.rest
ShadowAUS
ShadowAUSCOMMUNITY
Explore all skills by this author →
GitHub

iikit-04-testify

Generate Gherkin feature files with traceability tags and assertion hashes.

Updated Aug 27, 2026
Search Tags:#requirements#traceability#bdd#hashing#gherkin#test-driven-development#feature-files
One-click install
npx skills add https://github.com/ShadowAUS/chez-king-portal --skill iikit-04-testify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-04-testify
Source: https://github.com/ShadowAUS/chez-king-portal/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-04-testify
Command: npx skills add https://github.com/ShadowAUS/chez-king-portal --skill iikit-04-testify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generate executable Gherkin feature files from requirements artifacts before implementation. This enables true TDD by producing hash-locked BDD scenarios that serve as acceptance criteria and provide traceability from requirements to tests.

Core Features & Use Cases

  • Generate executable Gherkin .feature files from requirement artifacts before implementation.
  • Create hash-locked scenarios to lock acceptance criteria for test-driven development.
  • Maintain traceability with standard Gherkin tags and generated artifacts for verification.

Quick Start

Generate the first set of Gherkin features from your requirements with a single instruction: place the resulting .feature files under the feature's tests/features/ directory.

Frequently Asked Questions about iikit-04-testify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate executable Gherkin feature files from requirements?▼

Hash-locked BDD scenarios lock acceptance criteria by generating assertion hashes stored within the feature files. The skill validates these hashes to protect against tampering, ensuring acceptance criteria remain strictly enforced during red-green-refactor workflows.

What is traceability in test-driven development feature files?▼

You can use this approach for red-green-refactor workflows by generating hash-verified feature files before implementation. Running the scenarios produces red failures initially, and you implement code until the hash-locked acceptance criteria pass green.

Do I need specific test frameworks to run generated Gherkin feature files?▼

You do not need specific test frameworks bundled with the skill to run generated Gherkin feature files. The skill outputs standard .feature files that are compatible with any BDD framework supporting Gherkin syntax, which you place under tests/features/.

How do I prevent tampering with acceptance criteria in BDD scenarios?▼

To prevent tampering with acceptance criteria in BDD scenarios, the skill locks them using assertion hashes. It stores and continuously validates these hashes against the generated feature files to detect and block any unauthorized modifications.

Related Skills

Explore More Software Engineering Skills→
forztfforztf
9

speckit-analyze-zh

Parse spec.md, plan.md, and tasks.md to generate a structured consistency and quality report.

Community
Advanced
alexsandrocruzalexsandrocruz
6

test-driven-development

Enforce test-driven development with red-green-refactor cycles and failing tests first.

Community
Intermediate
pantheon-orgpantheon-org
9

bdd-testing

Create and run Cucumber BDD tests using Gherkin syntax and feature files.

Official
Advanced
GrimblazGrimblaz
3

bdd-scenarios

Automate Given/When/Then scenario authoring with ID traceability and CE Gate coverage detection.

Community
Advanced