qa-test-strategy

Spawn a qa-engineer to validate test coverage against acceptance criteria.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill qa-test-strategy-paulingham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-strategy
Source: https://github.com/paulingham/.claude/tree/main/skills/qa-test-strategy
Command: npx skills add https://github.com/paulingham/.claude --skill qa-test-strategy-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the Test phase by coordinating a qa-engineer to validate test coverage against acceptance criteria and write missing tests, reducing manual testing effort.

Core Features & Use Cases

  • Spawns a qa-engineer to map acceptance criteria to tests
  • Identifies coverage gaps and writes integration/E2E tests
  • Works with worktree-based test authoring to isolate changes

Quick Start

Analyze the feature's acceptance criteria and generate tests.

Frequently Asked Questions about qa-test-strategy

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

FAQPage Schema
How do I automate test coverage validation against acceptance criteria?

Automate test coverage validation against acceptance criteria by spawning a qa-engineer to map criteria to tests, identify coverage gaps, and write missing integration and E2E tests automatically.

How do I write missing integration and E2E tests for feature changes?

Write missing integration and E2E tests for feature changes by using an automated qa-engineer to analyze acceptance criteria and generate tests within isolated worktree-based environments.

When should I run automated test generation in my development workflow?

Run automated test generation after the Verify phase passes and before the Accept phase to ensure robust validation across feature changes before final delivery.

Can I use worktree-based test authoring to isolate QA changes?

Yes, you can use worktree-based test authoring to isolate QA changes, allowing the spawned qa-engineer to map acceptance criteria and write tests without affecting the main branch.

What is the best way to map acceptance criteria to automated tests?

The best way to map acceptance criteria to automated tests is by orchestrating a qa-engineer that systematically evaluates coverage gaps and writes missing tests for robust validation.