aiox-qa

Identify test requirement gaps, traceability, and risk for QA gates.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Andre-cardia/nivel-ia --skill aiox-qa-andre-cardia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-qa
Source: https://github.com/Andre-cardia/nivel-ia/tree/main/.claude/skills/AIOX/agents/qa
Command: npx skills add https://github.com/Andre-cardia/nivel-ia --skill aiox-qa-andre-cardia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quinn provides a thorough QA analysis and gate decisions to ensure test coverage, risk management, and compliance across software projects.

Core Features & Use Cases

  • Comprehensive test-architecture review and risk assessment
  • Requirements traceability mapping stories to tests using Given-When-Then
  • Quality gates, test design guidance, and actionable improvement recommendations
  • Real-world scenarios: evaluate epics, features, and stories to drive reliable releases

Quick Start

Ask me to review a story by ID and I will deliver a structured QA analysis and gate decision.

Frequently Asked Questions about aiox-qa

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

FAQPage Schema
What is requirements traceability and how does it map stories to tests?

Requirements traceability links stories to tests using Given-When-Then syntax. It verifies coverage and identifies gaps in test requirements to inform reliable quality gates and drive actionable test design.

How do I assess test architecture and risk for a specific feature story?

To assess test architecture and risk, review the story by ID to generate a structured QA analysis. This process evaluates non-functional requirements, calculates risk scores, and produces actionable improvement recommendations.

Can I use QA gate decisions to evaluate epics and features across software projects?

Yes, you can apply QA gate decisions to evaluate epics, features, and stories across software projects. This ensures comprehensive test coverage, risk management, and compliance while documenting gate decisions for full traceability.

What is the best way to identify gaps in test requirements and non-functional requirements?

The best way to identify gaps in test requirements is through a comprehensive test-architecture review. This process verifies non-functional requirements, guides test design, and documents gate decisions to ensure full traceability.

When do I need a QA risk assessment for my software release?

You need a QA risk assessment when evaluating epics, features, and stories to drive reliable releases. It calculates risk scores, identifies coverage gaps, and provides actionable improvement recommendations to ensure compliance.