verify-criteria

Validate acceptance criteria with test evidence and production risk analysis.

3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/scute-sh/scute --skill verify-criteria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-criteria
Source: https://github.com/scute-sh/scute/tree/main/.claude/skills/verify-criteria
Command: npx skills add https://github.com/scute-sh/scute --skill verify-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all defined acceptance criteria for a feature or task are rigorously met, providing a clear demonstration of completion and correctness before shipping or final review.

Core Features & Use Cases

  • Criterion Verification: Systematically checks each acceptance criterion against provided test evidence or alternative proof.
  • Comprehensive Testing: Mandates the execution of the full test suite to confirm all tests pass.
  • Quality Assurance: Includes a self-review process and prompts consideration of potential production issues not covered by tests.
  • Use Case: Before merging a new feature, use this Skill to confirm that all user stories have corresponding tests, the code passes all checks, and documentation is updated.

Quick Start

Use the verify-criteria skill to confirm that all acceptance criteria for the user story have been met and all final checks have passed.

Frequently Asked Questions about verify-criteria

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

FAQPage Schema
How do I verify acceptance criteria are met before shipping a feature?

To verify acceptance criteria before shipping, you validate each requirement against provided test evidence or alternative proof. This enforces a comprehensive checklist including full test suite execution, commit history review, and documentation updates to ensure production readiness.

What is the process for checking if code is production-ready?

Checking if code is production-ready involves completing a comprehensive quality gate checklist. This includes running the full test suite, performing a self-assessment, analyzing potential production risks not covered by tests, and reviewing commit history for final validation.

How do I ensure all user stories have corresponding tests before a code review?

To ensure user stories have corresponding tests before a code review, systematically check each acceptance criterion against demonstrable test evidence. This validation process confirms all defined requirements are met and all final quality checks pass.

Does this verification process require passing the full test suite?

Yes, the verification process requires passing the full test suite. It mandates full test suite execution to confirm all tests pass, ensuring the feature meets defined quality gates and is demonstrably ready for production.

What is included in a pre-merge quality assurance checklist?

A pre-merge quality assurance checklist includes criterion verification against test evidence, full test suite execution, self-assessment review, production risk analysis, and documentation updates. This ensures a feature meets all defined requirements before final review.

Why should I analyze production risks not covered by tests?

Analyzing production risks not covered by tests is necessary to ensure comprehensive quality assurance. It prompts consideration of potential production issues beyond automated tests, verifying the feature is truly production-ready and meets all defined quality gates.