What it does
Confirms the expected 29119-3 work products exist and are current, sample-checks the bidirectional traceability chain (at least one per critical risk area), assesses ISTQB/ISO 29119 process conformance, verifies retained execution evidence and sign-offs, and lists every gap with a severity, remediation, and owner. It alters no existing record — only the readiness report.
When to use it
Before an internal or external audit or compliance review.
Prerequisites
qa.config.yml — paths, tooling toggles, gates, risk_areas (assumes conservative defaults if missing). Reads existing QA docs and standards references (ISTQB-COMPLIANCE.md / ISTQB-AUDIT.md).
Output
Audit-readiness evidence pack over the 29119-3 work product set (no dedicated 29119-3 template) -> <paths.docs_dir>/AUDIT-READINESS-<scope>.md.
Mechanics
How it works
- Config guard; resolve scope from args or default to ISTQB/ISO 29119-3 conformance on risk_areas.critical
- Check documentation completeness: each work product present / present-but-outdated / missing
- Sample-check the bidirectional traceability chain (≥1 per critical area, min 3); mark intact or break
- Assess ISTQB / ISO 29119 process conformance per activity (conformant/partial/non-conformant)
- Confirm retained execution evidence, sign-offs, env/config management, defect lifecycle
- List severity-ordered gaps with remediation and owners; write the evidence pack
Why it works
The theory behind it
Test documentation, traceability & conformance evidence (CTFL §1.4.4; ISO/IEC/IEEE 29119-3). Auditability rests on bidirectional traceability being intact and work products being named to the standard; the pass names what it does NOT cover (unsampled chains) rather than implying audit-ready certainty (Principle 1).
CTFL v4.0 §1.4.4 · ISO/IEC/IEEE 29119-3
Example
See it in use
> /qa:audit-prep "ISO-29119"✓ Correct when It assembles a traceability + evidence pack and flags conformance gaps by severity.
Related commands
Used by