skills.rest
solace-ill
solace-illCOMMUNITY
Explore all skills by this author →
GitHub

test-evidence-review

Evaluate test evidence against acceptance criteria and produce per-story verdicts.

Updated Apr 26, 2026
Search Tags:#sign-off#test-coverage#evidence-quality#automation-testing#software-testing#qa-review#test-evidence
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill test-evidence-review-solace-ill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/solace-ill/vector-flow --skill test-evidence-review-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, automated approach to evaluating the quality of test files and evidence documents, going beyond mere existence checks to verify coverage, edge cases, and sign-offs for QA readiness.

Core Features & Use Cases

  • Reviews test coverage: assesses assertion counts, edge cases, and naming quality for automated tests.
  • Evaluates evidence quality: checks linkage to acceptance criteria, sign-offs, and artefact completeness.
  • Generates per-story verdicts (ADEQUATE, INCOMPLETE, MISSING) and aggregates an overall sprint verdict.

Quick Start

Run a full evidence review for the current sprint by invoking /test-evidence-review sprint.

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 test evidence coverage against acceptance criteria for a sprint?▼

You can review test evidence across a sprint by collecting test paths and evidence documents, evaluating assertion coverage and criterion linkage, and generating per-story verdicts of ADEQUATE, INCOMPLETE, or MISSING.

What does automated test evidence review check for QA readiness?▼

Automated test evidence review evaluates QA readiness by checking assertion coverage, edge-case handling, naming quality, sign-off completeness, artefact presence, and evidence freshness to validate readiness.

How do I review test evidence for a single story versus an entire epic?▼

Test evidence review scales from a single story to a sprint or epic by locating test evidence across unit, integration, and QA repository locations, generating structured verdicts for each scope.

Can I aggregate per-story test evidence verdicts into an overall sprint verdict?▼

Yes, test evidence review generates per-story verdicts of ADEQUATE, INCOMPLETE, or MISSING and aggregates them into an overall sprint verdict to summarize QA readiness.

What is the best way to identify gaps between test evidence and acceptance criteria?▼

Identify gaps by evaluating evidence documents for criterion linkage, artefact presence, and sign-off completeness, while checking automated tests for assertion coverage and edge-case handling.

When do I need a structured test evidence review for sign-off?▼

You need a structured test evidence review for sign-off when verifying that assertion coverage, edge-case handling, artefact presence, and criterion linkage meet QA readiness requirements before release.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

test-evidence-review

Audit test evidence quality and story readiness across sprints.

Community
Advanced
einja-inceinja-inc
1

task-qa

Execute mandatory tests and record failure classifications for QA evidence.

Official
Advanced
CarlosQ96CarlosQ96

test-evidence-review

Review test evidence and produce ADEQUATE, INCOMPLETE, or MISSING verdicts per story.

Community
Advanced
MichaelSolatiMichaelSolati

test-evidence-review

Evaluate automated tests and manual evidence for unverified acceptance criteria.

Community
Intermediate