qa-manager

Translate PRDs into QA strategies, test plans, and release criteria.

Updated May 8, 2026
One-click install
npx skills add https://github.com/ace3/skills --skill qa-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-manager
Source: https://github.com/ace3/skills/tree/main/skills/qa-manager
Command: npx skills add https://github.com/ace3/skills --skill qa-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA management translates product intent, PRD, and engineering plans into a structured, audit-ready QA strategy, coverage plan, and release judgment. It coordinates requirements analysis, risk classification, test strategy, test planning, test case design, defect processes, QA reporting, and release sign-off, without performing automated test execution.

Core Features & Use Cases

  • Turn PRDs and requirements into test strategy, acceptance criteria, and traceability mappings.
  • Define risk-based QA plans, go/no-go criteria, and audit-style release reports.
  • Design test cases and coverage using PICT or combinatorial methods, and coordinate defect reporting.

Quick Start

Produce a complete QA strategy and release sign-off plan from the provided PRD or requirements document.

Frequently Asked Questions about qa-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn PRD requirements into a structured test strategy?

To turn PRD requirements into a test strategy, translate product intent into structured requirements analysis, risk classification, and test planning. This yields an audit-ready QA strategy with traceability mappings, acceptance criteria, and defined release sign-off parameters.

What is risk-based test planning and when do I need it for release sign-off?

Risk-based test planning prioritizes testing efforts by classifying requirement risks to define go/no-go criteria. You need it for release sign-off to provide evidence-based findings, ensure traceability, and generate audit-style release reports that highlight critical defects.

How do I design test cases using combinatorial methods for requirements analysis?

Design test cases using PICT or combinatorial methods to maximize coverage from requirements analysis. This process coordinates test case design by mapping combinatorial inputs to acceptance criteria, ensuring structured defect reporting and traceability without writing automated test code.

Can I use this QA manager approach for automated test execution?

No, you cannot use this approach for automated test execution. The QA strategy explicitly routes actions to appropriate QA roles for test planning and defect reporting, defining coverage and release criteria without performing the automated test execution itself.

What's the best way to define go/no-go criteria for a QA release report?

The best way to define go/no-go criteria is through risk classification and requirements analysis during test planning. This generates an audit-style QA release report with evidence-based findings, defect reporting, and risk highlighting to justify the final release sign-off.