review-epic

Automates QA epic review by verifying TASKS.md completeness and producing a report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often slog through epic reviews, risking inconsistencies and delays. This skill standardizes the process, guiding reviewers to verify inputs, cross-check changes, run validations, and publish a clear verdict.

Core Features & Use Cases

  • Orchestrates a holistic epic review by validating brief.md, Engineer's done message, and TASKS.md.
  • Verifies task completeness, aligns work with the epic brief, and ensures traceability across artifacts.
  • Executes a runnable verification pass and runs the test suite to produce a definitive verdict.
  • Generates a structured QA report in the war-room and communicates outcomes to the team.

Quick Start

Initiate an epic review by loading brief.md, the engineer's done message, and TASKS.md for the current war-room.

Frequently Asked Questions about review-epic

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

FAQPage Schema
How do I automate epic QA reviews for war-room contexts?

Automated epic QA reviews in a war-room context standardize the verification process by validating brief.md, TASKS.md, and engineer done messages. This ensures consistent task tracking and reduces review delays across cross-functional teams.

What is the best way to verify TASKS.md completeness during a code review?

Verifying TASKS.md completeness during a code review involves cross-checking listed tasks against the epic brief and engineer's done message. This alignment guarantees traceability across artifacts before running any executable test suite.

How do I run a test suite and runnable verification for an epic review?

Running a test suite and runnable verification for an epic review executes automatically after code changes are audited. The process produces a definitive verdict confirming whether the implementation meets the documented acceptance criteria.

Can I generate a structured QA report after verifying epic acceptance criteria?

Generating a structured QA report after verifying epic acceptance criteria documents the final outcomes and communicates them to the team. This report summarizes the runnable verification pass and test execution results for the war-room.

What inputs do I need to start an epic review workflow?

Starting an epic review workflow requires loading brief.md, the engineer's done message, and TASKS.md for the current war-room. These artifacts provide the necessary context to guide the reviewer through the entire verification process.

Why standardize the epic review process instead of manual QA checks?

Standardizing the epic review process instead of manual QA checks prevents inconsistencies and delays caused by ad-hoc verification. It enforces a holistic audit of code changes, test execution, and acceptance criteria documentation.