gate-spec

Map acceptance criteria to implementation and test evidence in a codebase.

9|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-spec
Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/gate-spec
Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill gate-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that every requirement defined in a specification is demonstrably met by the implementation, preventing features from being shipped without proper backing.

Core Features & Use Cases

  • Evidence Mapping: Links acceptance criteria to specific lines of code and test cases.
  • Automated Verification: Checks for the presence of both implementation and test evidence for each criterion.
  • Use Case: After a developer implements a new feature based on a spec, this Skill automatically verifies that each acceptance criterion has corresponding code and passing tests, flagging any missing links.

Quick Start

Use the gate-spec skill to verify all acceptance criteria in the spec file.

Frequently Asked Questions about gate-spec

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

FAQPage Schema
How do I verify spec compliance with evidence in my codebase?

You can verify spec compliance by mapping every acceptance criterion from your specification to concrete implementation and test evidence. This automated verification checks for specific lines of code and passing tests, flagging any missing links.

What is the best way to check if all acceptance criteria have corresponding test cases?

Checking acceptance criteria involves parsing spec files and searching code and test files for evidence. This process generates a compliance matrix that ensures all defined requirements are demonstrably met before release.

How do I link acceptance criteria to specific lines of code automatically?

Linking acceptance criteria to specific lines of code is achieved through evidence mapping. The system parses your specification and searches your codebase to automatically verify that each criterion has corresponding implementation and test evidence.

Can I prevent the release of unverified features using specification mapping?

Preventing the release of unverified features is the primary goal of specification mapping. By ensuring every requirement is demonstrably met and generating a compliance matrix, it stops incomplete features from shipping without proper backing.

Does automated spec verification work without external dependencies?

Automated spec verification works without external dependencies. It relies on parsing spec files and searching internal code and test files to generate a compliance matrix, ensuring all defined requirements are demonstrably met.

What format does the compliance matrix use when parsing spec files?

The compliance matrix generated from parsing spec files maps every acceptance criterion to concrete implementation and test evidence. It highlights whether each defined requirement has corresponding code and passing tests, flagging any missing links.