test-evidence-review

Evaluate automated tests and manual evidence for unverified acceptance criteria.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill test-evidence-review-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-evidence-review
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/test-evidence-review
Command: npx skills add https://github.com/MichaelSolati/mkai --skill test-evidence-review-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unverified story acceptance criteria slipping through QA sign-off due to low-quality automated tests or incomplete manual evidence documents, which can lead to undetected bugs or incomplete feature delivery.

Core Features & Use Cases

  • Automated Test Quality Review: Evaluates Logic and Integration story tests for assertion coverage, edge case handling, naming conventions, and formula traceability to catch thin or vacuous tests.
  • Manual Evidence Validation: Reviews Visual/Feel and UI story evidence documents for complete acceptance criterion linkage, required sign-offs, screenshot/walkthrough artefacts, and freshness.
  • Use Case: Before finalizing a sprint, run this skill to identify blocking issues like missing test assertions or absent QA sign-offs that would prevent stories from being marked complete.

Quick Start

Use the test-evidence-review skill to audit the test quality and evidence completeness for all stories in the current sprint before QA hand-off.

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 coverage for story acceptance criteria before QA sign-off?

Test evidence review evaluates automated test files and manual evidence documents to identify unverified story acceptance criteria before QA sign-off. It enforces quality standards for assertion coverage, edge case handling, and evidence criterion linkage across Logic, Integration, Visual/Feel, and UI story types.

What does a sprint audit for test quality and evidence completeness involve?

A sprint audit for test quality reviews automated tests for assertion coverage, naming conventions, and formula traceability, while validating manual evidence documents for required sign-offs, screenshot artefacts, and freshness to ensure stories meet completion standards.

Can I scope a test evidence review to individual stories instead of a full sprint?

Yes, test evidence review supports scoped reviews of individual stories, entire sprints, or full epics. You can target specific Logic, Integration, Visual/Feel, or UI story types to evaluate assertion coverage and evidence completeness before QA hand-off.

How do I validate manual evidence documents for Visual and UI story types?

Manual evidence validation reviews Visual/Feel and UI story evidence documents for complete acceptance criterion linkage, required sign-offs, screenshot or walkthrough artefacts, and artefact freshness to ensure no unverified criteria slip through QA.

What are common issues blocking story completion during test evidence review?

Common blocking issues identified during test evidence review include missing test assertions, absent QA sign-offs, incomplete acceptance criterion linkage, vacuous tests lacking edge case handling, and stale evidence artefacts that prevent stories from being marked complete.

Do I need any specific testing frameworks to run a test evidence review?

No specific testing frameworks are required as dependencies. The test evidence review skill evaluates automated test files and manual evidence documents directly to enforce quality standards for assertion coverage, naming conventions, and formula traceability across your existing software development workflow.