Skip to content

gracefullight/pkgs / .agents/skills/oma-qa

oma-qa

Verified

Review changes for correctness, security, accessibility, and performance. Use for scoped quality reviews or verification plans; bug fixes use oma-debug.

resources/iso-quality.md

View on GitHub
# QA Agent - ISO Quality Guide

Use this file when the user asks for standards-based QA suggestions, enterprise audit readiness, or process-oriented quality improvements.

## Positioning

- Use **ISO/IEC 25010** as the practical software quality model.
- Treat **ISO/IEC 25010** as part of the **ISO/IEC 25000 SQuaRE family** when users say "ISO 25000".
- Use **ISO/IEC 29119** for test process, test design, traceability, and evidence recommendations.
- Do not force standards language into every QA review. Add it when it improves decision quality, auditability, or delivery discipline.

## 1. ISO/IEC 25010 Mapping

Map findings to these quality characteristics when relevant:

- functional suitability
- performance efficiency
- compatibility
- usability
- reliability
- security
- maintainability
- portability

Use this mapping to answer:

- Which quality areas are under-covered?
- Which areas are blocking release confidence?
- Which missing tests leave important quality characteristics unverified?

## 2. ISO/IEC 29119 Suggestions

Recommend these when test discipline is weak:

- test strategy or test plan
- test levels and scope definition
- requirement / risk to test traceability
- explicit test conditions and expected results
- risk-based prioritization
- entry / exit criteria
- evidence retention for review or audit

## 3. When to Mention Standards

Mention ISO alignment when:

- the user asks for audit readiness
- the work is enterprise or regulated
- release governance is unclear
- testing exists but lacks structure or traceability
- quality discussion is too vague and needs a common model

Avoid overusing standards language when:

- the task is a quick bug fix
- the user wants only concrete defects
- standards language would add ceremony without action

## 4. Review Output Pattern

If standards are relevant, add a short section:

```md
## Standards Alignment

### ISO/IEC 25010
- Quality characteristic:
- Gap:
- Recommendation:

### ISO/IEC 29119
- Test governance gap:
- Traceability / evidence gap:
- Recommendation:
```

## 5. Guardrails

- Prefer practical suggestions over compliance theater
- Do not claim formal compliance unless evidence exists
- Tie every standards suggestion to a delivery, test, or risk outcome
- Keep standards comments secondary to concrete findings
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall