validation-and-review

Validate deliverables against acceptance criteria with compile checks, automated tests, and code review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/igot-ai/os-twin --skill validation-and-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validation-and-review
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-qa/validation-and-review
Command: npx skills add https://github.com/igot-ai/os-twin --skill validation-and-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deliverables often fail to clearly demonstrate alignment with defined acceptance criteria, leading to rework and delayed releases.

Core Features & Use Cases

  • Systematic validation of implementations against acceptance criteria, ensuring traceable quality gates.
  • Comprehensive QA workflow coverage including compile checks, automated tests, code reviews, and a formal walkthrough.
  • Use Case: A team runs validation at the end of a feature sprint to certify readiness for release and generate a walkthrough document.

Quick Start

Perform a validation pass on the latest build to verify all acceptance criteria are met and a walkthrough document is produced.

Frequently Asked Questions about validation-and-review

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

FAQPage Schema
How do I validate deliverables against acceptance criteria before a release?

To validate deliverables against acceptance criteria, perform a systematic validation pass covering compilation checks, automated tests, code reviews, and walkthrough documentation to certify release readiness and ensure traceable quality gates.

What is a quality gate process in software QA workflows?

A quality gate process is a systematic validation checkpoint in software QA workflows that verifies deliverables satisfy defined acceptance criteria through compilation, automated testing, code review, and walkthrough documentation before marking tasks as DONE.

How do I set up a code review and walkthrough workflow for feature sprints?

Setting up a code review and walkthrough workflow requires defining explicit acceptance criteria first, then running compilation checks and automated tests, and finally producing a formal walkthrough document to demonstrate alignment and certify readiness.

Do I need explicit acceptance criteria to run validation and QA checks?

Yes, explicit acceptance criteria are required to run validation and QA checks. The process needs these defined benchmarks to systematically validate implementations, produce reproducible test results, and generate traceable walkthrough documentation.

What is the best way to ensure code review acceptance criteria are met?

The best way to ensure code review acceptance criteria are met is to enforce a comprehensive quality gate that requires reproducible automated test results, a formal code review, and a documented walkthrough before any deliverable can be marked as DONE.

Why does my QA validation fail without a walkthrough document?

Your QA validation fails without a walkthrough document because the process requires a formal walkthrough to demonstrate that deliverables satisfy defined acceptance criteria and to mark tasks as DONE with traceable quality assurance.