test-evidence-review

Audit per-story test coverage and documentation to identify evidence gaps.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill test-evidence-review-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/test-evidence-review
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill test-evidence-review-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits test evidence across stories to ensure proper coverage and sign-off, reducing reliance on existence checks.

Core Features & Use Cases

  • Per-story verdicts evaluate whether test evidence meets acceptance criteria.
  • Gap analysis identifies missing tests and documentation across sprints.
  • Anti-pattern detection flags flaky tests, skipped tests, or stale artifacts.

Quick Start

Run this skill against in-sprint stories to generate per-story verdicts and identify evidence gaps.

Frequently Asked Questions about test-evidence-review

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

FAQPage Schema
How do I audit test evidence for acceptance criteria coverage in a sprint?

To audit test evidence for acceptance criteria coverage, evaluate per-story test artifacts against documented sign-offs to identify missing tests and documentation gaps across in-sprint stories.

What is test evidence gap analysis and when do I need it?

Test evidence gap analysis identifies missing tests and documentation across sprints by auditing unit, integration, and visual QA artifacts to ensure proper coverage and reduce reliance on simple existence checks.

Can I flag flaky or skipped tests during an in-sprint QA sign-off?

Yes, you can flag flaky or skipped tests during an in-sprint QA sign-off using anti-pattern detection, which evaluates deterministic tests and produces per-story verdicts highlighting stale artifacts.

How do I generate per-story verdicts for production story evidence?

Generate per-story verdicts for production story evidence by running an on-demand audit that checks acceptance criteria coverage, deterministic tests, and documented sign-off status across unit, integration, and visual QA artifacts.

Does this approach work for sprint reviews and on-demand audits?

Yes, this approach works for both in-sprint QA sign-offs and sprint reviews, as well as on-demand audits of production story evidence, producing per-story verdicts and highlighting anti-patterns like flaky tests.

Why does simple existence checking fail for test documentation?

Simple existence checking fails for test documentation because it does not verify acceptance criteria coverage or enforce deterministic test checks, missing anti-patterns like flaky tests, skipped tests, or stale artifacts.