One-click install
npx skills add https://github.com/GustaPaes/aiox-sprint-canvas --skill aiox-qa-gustapaes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-qa
Source: https://github.com/GustaPaes/aiox-sprint-canvas/tree/main/.claude/skills/AIOX/agents/qa
Command: npx skills add https://github.com/GustaPaes/aiox-sprint-canvas --skill aiox-qa-gustapaes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you validate and protect software quality by reviewing requirements traceability, test strategy, non-functional requirements, and risk coverage before work proceeds too far.

Core Features & Use Cases

  • Comprehensive QA Reviews & Quality Gates: Run structured story reviews and produce PASS/CONCERNS/FAIL/WAIVED quality gate decisions with rationale.
  • Risk- and Evidence-Based Validation: Assess NFRs, generate a risk matrix, and verify evidence-based QA requirements and critical bug-fix thinking.
  • Test Architecture & Traceability: Map requirements to tests (Given-When-Then) and generate test designs/suites to ensure coverage.

Quick Start

Use the aiox-qa skill to review a specific story and decide whether it meets your quality gate by sending: "Run *review-build for story {story-id} and then *gate for {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 requirements traceability and quality gate decisions for software stories?

Automate requirements traceability by mapping requirements to Given-When-Then tests, then generate PASS, CONCERNS, FAIL, or WAIVED quality gate decisions with structured rationale for your software stories.

What is a pre-merge story audit for non-functional requirements and risk coverage?

A pre-merge story audit validates requirements traceability, test strategy, and non-functional requirement coverage, generating a risk matrix to ensure evidence-based QA verification before code proceeds too far.

Can I assess security scans and non-functional requirements without a dedicated QA tool?

Yes, you can assess non-functional requirements by validating risk coverage and evidence-based QA requirements directly within your codebase, applying structured review phases and advisory outputs for implementation follow-ups.

How do I map Given-When-Then test architecture to validate requirements coverage?

Map requirements to tests by generating test designs and suites using Given-When-Then structures, validating traceability and ensuring complete test architecture coverage across the targeted software stories.

Does this quality gate approach work for evidence-based QA verification across large codebases?

Yes, evidence-based QA verification applies across codebases to validate test strategy, critical bug-fix thinking, and risk coverage, producing advisory outputs suitable for implementation follow-ups.

Why does my QA review fail to catch non-functional requirement risks before merging?

QA reviews fail when lacking structured risk assessment and requirements traceability mapping; applying gate governance decisions and evidence-based verification prevents missing non-functional requirement risks.