aiox-review-story

Reviews a development story and writes a QA gate verdict with lifecycle status transitions.

3.1k|952|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/SynkraAI/aios-core --skill aiox-review-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-review-story
Source: https://github.com/SynkraAI/aios-core/tree/main/.grok/skills/aiox-review-story
Command: npx skills add https://github.com/SynkraAI/aios-core --skill aiox-review-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enforces a consistent quality gate on completed development stories, producing a formal PASS/CONCERNS/FAIL/WAIVED verdict and driving the story's lifecycle status instead of relying on ad-hoc review.

Core Features & Use Cases

  • QA Gate Execution: Loads the qa-gate task definition as the source of truth, reviews the story, and writes a gate file under docs/qa/gates/.
  • Lifecycle Transitions: Updates the story's QA Results section and applies canonical status changes (Done for PASS/CONCERNS/WAIVED, back to InProgress for FAIL).
  • Anti-Self-Review Guardrails: Forbids the implementing agent from approving its own work and prohibits git push during the gate.
  • Use Case: After a developer finishes a story, invoke the gate with the story path to get a recorded verdict, a gate file on disk, and an updated story status in one pass.

Quick Start

Run the review-story gate on the story file at docs/stories/my-story.md in interactive mode and record the verdict.

Frequently Asked Questions about aiox-review-story

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

FAQPage Schema
How do I run a QA gate review on a story?

Invoke the skill with the story path as the first argument and an optional mode (yolo or interactive) as the second. It loads the qa-gate task, performs the review, writes a gate file under docs/qa/gates/, and updates the story's QA Results section.

What verdicts can a QA gate produce?

The gate produces four verdicts: PASS, CONCERNS, FAIL, or WAIVED. PASS, CONCERNS, and WAIVED move the story to Done with a lifecycle transition entry, while FAIL returns it to InProgress with a list of fixes for apply-qa-fixes.

Can the same agent that implemented a story approve it?

No. The skill explicitly forbids self-approving as the same agent that implemented the story, enforcing an anti-self-review policy. The review adopts the @qa agent or the story's designated quality_gate agent.

What happens when a QA gate verdict is FAIL?

A FAIL verdict returns the story to InProgress status and lists the required fixes for the apply-qa-fixes workflow. The gate file and story QA Results section still record the verdict for traceability.

Where are QA gate files stored?

Gate files are written under docs/qa/gates/, with the exact path determined by the qa-gate task or core-config. The story's QA Results section is also updated with the verdict and the gate file path.