aiox-qa

Review stories against acceptance criteria, risks, and non-functional requirements for QA quality gates.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech --skill aiox-qa-hyagoviana
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-qa
Source: https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech/tree/main/meu-projeto/.claude/skills/AIOX/agents/qa
Command: npx skills add https://github.com/hyagoviana/Sistema_Hyago_Viana_Adabtech --skill aiox-qa-hyagoviana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AIOX QA helps teams prevent weak coverage and unclear acceptance by systematically validating test architecture, non-functional requirements, and quality gate decisions before code or stories move forward.

Core Features & Use Cases

  • Comprehensive QA & Gate Decisions: Runs structured story reviews and produces PASS/CONCERNS/FAIL/WAIVED outcomes with rationale to support reliable release decisions.
  • Risk-Based & NFR Validation: Assesses probability × impact risk and validates non-functional requirements (e.g., security, performance, reliability) through targeted checks.
  • Evidence & Traceability: Verifies evidence-based requirements and maps Given-When-Then patterns to ensure requirements trace back to tests.

Quick Start

Ask the QA agent to review a specific story and create a quality gate decision with: review-build story-id.

Frequently Asked Questions about aiox-qa

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

FAQPage Schema
How do I automate quality gate decisions for user stories in a CI pipeline?

Automate quality gate decisions by reviewing stories against acceptance criteria, risks, and non-functional requirements. This process generates PASS, CONCERNS, FAIL, or WAIVED outcomes with rationale to support reliable release decisions in pipeline-based QA workflows.

What is requirements traceability and how does it map to test architecture?

Requirements traceability maps Given-When-Then patterns to ensure requirements trace back to tests. It verifies evidence-based requirements and validates test architecture quality by systematically checking coverage against defined non-functional requirements.

How do I validate non-functional requirements like security and performance before release?

Validate non-functional requirements by assessing probability times impact risks and running targeted checks for security, performance, and reliability. This ensures comprehensive test design and enforces security validation across committed changes.

Can I enforce QA write-scope limits and operational guardrails in a YAML pipeline?

Yes, you can enforce QA write-scope limits and operational guardrails using a YAML-defined configuration. This restricts QA writing to the QA Results section while executing command-driven verification tasks for structured story reviews.

What's the best way to start a risk-based quality assessment for a specific story?

Start a risk-based quality assessment by issuing the command review-build story-id to the QA agent. This triggers a structured story review that produces quality gate decisions based on risk probability, impact, and evidence checks.