test-evidence-review

Evaluate test and evidence coverage against story acceptance criteria.

72|7|Updated Apr 29, 2026

Search Tags:#acceptance criteria #automated tests #test evidence #quality review #qa sign-off #documentation completeness #edge case coverage

Ready to run

npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill test-evidence-review-striderza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/test-evidence-review
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill test-evidence-review-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents stories from reaching QA sign-off with missing or weak verification by checking that test files and manual evidence documents actually cover the required behavior.

Core Features & Use Cases

Automated test quality review: Evaluates assertion coverage, edge-case handling, naming quality, and (for Logic stories) formula traceability.
Manual evidence quality review: Verifies criterion linkage, required sign-offs, referenced artefacts (screenshots/walkthroughs), and evidence freshness.
Scope-based auditing: Reviews a single story, an entire sprint, or all stories under a system/epic and produces ADEQUATE/INCOMPLETE/MISSING verdicts per story.

Quick Start

Run this skill to review a story’s test and evidence completeness and quality by executing: /test-evidence-review path/to/your-story.md

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema

How do I verify automated tests cover acceptance criteria before QA sign-off?▼

To verify automated tests before QA sign-off, evaluate assertion coverage, edge-case handling, and naming quality against the story's acceptance criteria. This review process ensures test files actually verify required behaviors and produces ADEQUATE, INCOMPLETE, or MISSING verdicts for each story.

What is manual test evidence review and how does it work?▼

Manual test evidence review verifies criterion linkage, required sign-offs, referenced artifacts like screenshots, and evidence freshness within documentation. It ensures manual evidence documents adequately verify a story's acceptance criteria before reaching QA sign-off by inspecting the provided files.

How do I audit test evidence quality across an entire sprint or system epic?▼

To audit test evidence quality across a sprint or system epic, perform scope-based auditing on all included stories. The review analyzes assertion coverage and evidence completeness per story, generating a dated evidence-review report with ADEQUATE, INCOMPLETE, or MISSING verdicts for the entire batch.

Can I review test evidence for different story types like Logic, Integration, and UI?▼

Yes, you can review test evidence for Logic, Integration, Visual/Feel, UI, and Config/Data story types. The review evaluates specific requirements for each type, such as formula traceability for Logic stories, ensuring automated tests and manual evidence adequately verify the required behavior.

What's the best way to check edge case coverage in automated tests?▼

The best way to check edge case coverage in automated tests is via read-only inspection of the test files. The review evaluates assertion quality and edge-case handling against the story's acceptance criteria to determine if the tests adequately verify required behaviors.

Does the test evidence review process modify my existing test files?▼

No, the test evidence review process does not modify existing test files. It performs a read-only inspection of automated tests and manual evidence documents to analyze assertion and coverage quality, producing verdicts and an optional dated report without altering your source files.