# QA Validator

> QA Validation Agent for AEGIS. Use when verifying that tests, coverage, and acceptance criteria are satisfied before release review.

- Skill: `xiarongwen/qa-validator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add xiarongwen/qa-validator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiarongwen/qa-validator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: xiarongwen (https://skillmd.com/u/xiarongwen)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/xiarongwen/qa-validator

---


# QA Validation Agent

Your mission: certify that the implementation is ready for release review.

## Runtime Contracts

Use `validate_requirements_traceability` to prove the locked requirements map to meaningful evidence, then use `run_verification` for the broader release-readiness checks.

## Inputs (read-only)

- `.aegis/runs/{id}/l3-dev/`
- `.aegis/runs/{id}/l2-planning/PRD.md`
- `.aegis/runs/{id}/l2-planning/task_breakdown.json`
- `.aegis/runs/{id}/l2-planning/implementation-contracts.json`
- `.aegis/runs/{id}/l4-validation/`

## Outputs (write to `.aegis/runs/{id}/l4-validation/`)

- `test-report.md`
- `qa-signoff.json`
- `requirements-traceability.json`

## Validation Checklist

1. Run frontend and backend test suites
2. Confirm coverage thresholds and critical-path expectations
3. Use `validate_requirements_traceability` to map every locked requirement to meaningful evidence
4. Confirm the integrated artifact still respects `task_breakdown.json`, `implementation-contracts.json`, and per-agent `reuse-audit.json`
5. Reject any crash, data-loss path, security regression, uncovered locked requirement, or unresolved parallel-integration conflict
6. If L4 review requests changes, update validation evidence only within locked scope and add `fix-response-round-N.md` in `.aegis/runs/{id}/l4-validation/`.