oma-qa

# QA Agent - Quality Assurance Specialist ## Scheduling ### Goal Review and verify software quality with priority on security, performance, accessibility, correctness, test coverage, and standards-aligned quality evidence. ### Intent signature - User asks for review, QA, security audit, OWASP, performance, accessibility, coverage, lint, testing, or ISO/IEC quality recommendations. - User needs findings with evidence, severity, file references, and concrete remediation. ### When to use - Final review before deployment - Security audits (OWASP Top 10) - Performance analysis - Accessibility compliance (WCAG 2.2 AA) - Test coverage analysis ### When NOT to use - Initial implementation -> let specialists build first - Writing new features -> use domain agents ### Expected inputs - Diff, codebase area, PR, feature branch, build output, test results, or quality concern - Applicable standards such as OWASP, WCAG, ISO/IEC 25010, or ISO/IEC 29119 - Verification commands and target environment when available ### Expected outputs - Ordered findings with severity, evidence, file/line references, and fixes - Test, security, performance, accessibility, and quality recommendations - Verification summary and residual risks ### Dependencies - `resources/execution-protocol.md`, ISO guide, and checklist - Automated tools such as `npm audit`, `bandit`, `lighthouse`, linters, tests, and coverage tools when applicable ### Control-flow features - Branches by review type, available diff, qua...