review

Review story artefacts and emit severity-tagged findings with diffs.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill review-heymishy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/review
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill review-heymishy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews story artefacts for quality, completeness, traceability, and scope discipline. Produces structured findings with HIGH/MEDIUM/LOW severity. On re-runs, produces a diff showing exactly what changed. HIGH findings block progression to /test-plan. Use when stories exist and someone says "review the stories", "check the definition", "quality check", "re-review", or moves past definition. Run per story or per epic batch.

Core Features & Use Cases

  • Deterministic findings and severity tagging to surface issues quickly.
  • Re-run compatibility with exact diffs to track changes over time.
  • Enforces entry conditions (stories, parent epic, benefit-metric, discovery artefact) before generating a report.
  • Produces a structured report that guides next steps, including test-plan gating.

Quick Start

Run a review pass on a single story or an epic batch to generate findings and a diff for changes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a quality review on story artefacts before test planning?

To run a quality review on story artefacts, execute a per-story or epic-batch review pass. It validates entry conditions like parent epic and discovery artefacts, then emits deterministic findings with HIGH, MEDIUM, or LOW severities to guide test planning.

What is a deterministic story quality review and how does it work?

A deterministic story quality review applies structured rules loaded from artefact frontmatter to validate scope, completeness, and traceability. It produces consistent findings with severity tags and re-run diffs showing exactly what changed between passes.

What artefacts are required to run a story quality check?

Running a story quality check requires stories, a parent epic, a discovery artefact, and a benefit-metric artefact. The review enforces these entry conditions before validating scope discipline and generating a structured report.

Can I re-review stories to see exactly what changed since the last pass?

Yes, you can re-review stories to see exactly what changed. Re-running the review produces a diff against previous findings, allowing you to track changes over time and verify if HIGH severity issues blocking progression were resolved.

What happens when a story quality review finds HIGH severity issues?

When a story quality review finds HIGH severity issues, it blocks progression to the test-plan phase. The structured report surfaces these scope, completeness, or traceability issues to guide necessary fixes before moving forward.