qa-process

What problem does it solve?

QA and quality engineering processes often become inconsistent or incomplete, leading to regressions, uncovered edge cases, and releases that fail under real-world conditions.

Core Features & Use Cases

• Test strategy planning (pyramid of tests): Defines how much testing to allocate across unit, integration, and E2E based on risk and user-critical paths.
• Definition of Done (acceptance criteria): Establishes clear, actionable release gates for normal and critical features, including security and failure-mode validation.
• Edge case analysis checklist: Covers common data/state/dependency/HTTP boundary failures, including concurrency, retries, idempotency, and malformed inputs.
• Regression planning and CI quality gates: Specifies what to run on every PR, before release, and periodically, plus measurable thresholds for coverage and defect prevention.
• Quality reporting template: Provides a structured way to document coverage, edge cases, risks, and go/no-go decisions.

Quick Start

Use the qa-process skill to design a complete QA plan for a specific feature by providing its scope and risk level (normal vs critical) and then asking for acceptance criteria, edge cases to cover, and the recommended CI quality gates.