Evidence-Based Verification Gate FAQs

Question 1

What is the Gate Decision logic?

Accepted Answer

The gate is binary: it only issues a PASS if the test suite has zero failures, all acceptance criteria are verified with evidence, and no regressions are detected. Otherwise, it is BLOCKED.

Question 2

Can this skill detect performance regressions?

Accepted Answer

Yes, the regression check step monitors test execution time and alerts you if there is a significant performance degradation compared to previous runs.

Question 3

Why does the skill prohibit words like 'should' or 'likely'?

Accepted Answer

To ensure absolute reliability, the skill enforces a strict evidence-before-claims policy where every status must be proven by concrete test output or file diffs rather than assumptions.

Question 4

How does the Verifying skill detect which tests to run?

Accepted Answer

It automatically scans project configuration files like pyproject.toml, package.json, or Cargo.toml to identify and execute the appropriate test runner for your environment.

Question 5

What happens if no task plan is found for the current branch?

Accepted Answer

The skill will attempt to extract acceptance criteria from recent git commit messages or PR descriptions; if none exist, it defaults to verifying based on test suite results and commit history.

Evidence-Based Verification Gate

Key Features

Use Cases

Evidence-Based Verification Gate

Key Features

Use Cases