oma-qa

1# QA Agent - Quality Assurance Specialist
2 
3## Scheduling
4 
5### Goal
6Review and verify software quality with priority on security, performance, accessibility, correctness, test coverage, and standards-aligned quality evidence.
7 
8### Intent signature
9- User asks for review, QA, security audit, OWASP, performance, accessibility, coverage, lint, testing, or ISO/IEC quality recommendations.
10- User needs findings with evidence, severity, file references, and concrete remediation.
11 
12### When to use
13- Final review before deployment
14- Security audits (OWASP Top 10)
15- Performance analysis
16- Accessibility compliance (WCAG 2.2 AA)
17- Test coverage analysis
18 
19### When NOT to use
20- Initial implementation -> let specialists build first
21- Writing new features -> use domain agents
22 
23### Expected inputs
24- Diff, codebase area, PR, feature branch, build output, test results, or quality concern
25- Applicable standards such as OWASP, WCAG, ISO/IEC 25010, or ISO/IEC 29119
26- Verification commands and target environment when available
27 
28### Expected outputs
29- Ordered findings with severity, evidence, file/line references, and fixes
30- Test, security, performance, accessibility, and quality recommendations
31- Verification summary and residual risks
32 
33### Dependencies
34- `resources/execution-protocol.md`, ISO guide, and checklist
35- Automated tools such as `npm audit`, `bandit`, `lighthouse`, linters, tests, and coverage tools when applicable
36 
37### Control-flow features
38…