What problem does it solve?
This Skill prevents “it works on my machine” releases by requiring verifiable BDD scenarios before implementation and forcing evidence-based verification after changes.
Core Features & Use Cases
- Gate In (Plan-to-Code): Extracts and stores BDD scenarios in features.json (with
passes: false) before you start implementing.
- Gate Out (Verification Loop): Verifies each unpassed scenario with concrete evidence (tests preferred, runtime validation otherwise) and flips
passes: true only after successful observation.
- Optional Enforcement Hooks: Supports hard and soft enforcement via Claude hooks to block or remind at key moments in the workflow.
- Practical Scenario Guidance: Provides scenario quality checks, loop caps, and structured findings output.
Quick Start
Use the stop skill to turn your spec into features.json scenarios, implement only what those scenarios require, and then verify every scenario before marking the feature complete.