aiox-qa

To perform a QA review, run the command review STORY-ID against your story. This triggers a structured multi-phase analysis that assesses test architecture, validates risk profiles, and outputs deterministic quality gate decisions.

Requirements traceability verifies evidence-based requirements by mapping them to tests using Given-When-Then patterns. This mechanism improves test coverage and debuggability by ensuring every story expectation has corresponding test evidence.

Non-functional requirements validation occurs during the story readiness review by applying targeted checks for security, performance, and reliability. This assesses the story's risk profile to ensure it meets quality expectations before progression.

Yes, you can generate outcome-guided QA fix request artifacts for developers while strictly constraining edits to the allowed QA Results section. This ensures the rest of your story documentation remains untouched and stable.

The quality gate review process satisfies deterministic review workflows by constraining story updates exclusively to the QA Results section. It provides reliable gate decisions and evidence generation without altering external story content.

The best way to assess risk profiles is to execute a comprehensive QA review workflow for the specific story. This validates non-functional requirements, checks security scans, and generates actionable QA decisions for readiness.