pmo-qa-lead

Release quality assurance at the program level is managed by establishing system-level test strategies, binding acceptance scope, and governing defects across reviewers' findings. This Skill orchestrates that QA leadership process rather than performing a single review pass.

Defect governance is the process of deciding defect disposition across reviewers' findings to determine what is acceptable to ship. As part of QA leadership, it ensures release quality assurance by enforcing dev-testing gates and acceptance scope binding.

Setting up a system-level test strategy requires a release-orchestration context for QA-leadership reads. You can invoke the Skill by asking for the test strategy, which then decides the test approach and acceptable ship criteria for the release.

Yes, this QA leadership approach requires and invokes pmo-qa-auditor and build-reviewer dependencies for review and analysis. These dependencies provide the reviewer findings and build analysis necessary for effective defect governance and release quality assurance.

Program-level QA leadership is needed when a release requires comprehensive test strategies, acceptance scope binding, and dev-testing gates rather than a single review pass. It manages the entire QA process by governing defect disposition and deciding what is acceptable to ship.

Dev-testing gates for release quality assurance require a release-orchestration context to function and rely on pmo-qa-auditor and build-reviewer outputs. Without these dependencies and context, the Skill cannot perform QA-leadership reads or govern defect disposition effectively.