test-strategy

Generate a multi-quarter QA strategy document with risk matrices, pyramid analysis, and quality gates.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill test-strategy-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-strategy
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/test-strategy
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill test-strategy-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often accumulate test suites without a plan, ending up with slow CI pipelines, inverted test pyramids, and no measurable quality targets. This Skill produces an actionable multi-quarter QA strategy document that ties scope, risk prioritization, tooling, and metrics into one living document. ## Core Features & Use Cases - Risk-Based Prioritization: Score features on a 5x5 impact-by-likelihood matrix and map each risk band to a concrete testing action. - Test Pyramid Diagnosis: Identify whether the suite is a healthy pyramid, ice cream cone, diamond, or hourglass, then get a phased rebalance plan. - Quality Gates & KPIs: Define PR, merge, deploy, and nightly gates with concrete pass/fail thresholds plus a metrics table covering coverage, flakiness, escape rate, and MTTR. - Use Case: A team with 150 E2E tests and a 52-minute pipeline uses this Skill to diagnose the inverted pyramid, decompose E2E tests into unit tests, and roll out a four-phase plan that brings CI under 15 minutes. ## Quick Start Ask the assistant to create a QA strategy document for your product, describing your tech stack, team size, current test counts, and release cadence.

Frequently Asked Questions about test-strategy

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

FAQPage Schema
How do I write a QA test strategy document?

Start with discovery questions about product context, current test state, and team constraints, then fill a 13-section template covering scope, test levels, pyramid analysis, risk matrix, environments, tools, gates, metrics, and timeline. Each section must name a measurable KPI and an owner.

What is a good test pyramid ratio for unit, integration, and E2E tests?

The recommended target is 70-80% unit tests, 15-20% integration tests, and 5-10% E2E tests. If E2E tests outnumber unit tests, the suite is an inverted ice cream cone, which causes slow CI and high maintenance.

How do I fix an inverted test pyramid with too many E2E tests?

Freeze new E2E test creation, decompose existing E2E tests that validate unit-level logic into lower-level tests, require unit tests in every PR touching business logic, and set CI gates on the unit-to-E2E ratio.

What is the difference between a test strategy and a test plan?

A test strategy is a multi-quarter umbrella document defining direction, risk priorities, and quality gates. A test plan covers a single sprint or release and should be handled by a separate test-planning skill.

When should I not use this test strategy skill?

Do not use it for single-sprint or single-release planning, which belongs to test-planning, or for identifying which areas carry the most risk, which should be done first with risk-based-testing.