plan-test-strategy

Generate focused test strategies for software features by assessing risk and selecting test types.

4|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill plan-test-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-test-strategy
Source: https://github.com/cpliakas/claude-code-engineering-leaders/tree/main/skills/plan-test-strategy
Command: npx skills add https://github.com/cpliakas/claude-code-engineering-leaders --skill plan-test-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineers create efficient and effective test strategies, ensuring that the most critical aspects of a feature or component are tested while avoiding unnecessary effort.

Core Features & Use Cases

  • Risk Assessment: Analyzes a feature's blast radius, change frequency, failure cost, complexity, and external coupling to determine appropriate test investment.
  • Test Type Selection: Recommends the lowest effective layer for testing (unit, integration, e2e, etc.) with clear rationale.
  • Brittleness Analysis: Identifies and suggests mitigations for tests that are prone to breaking due to implementation changes.
  • Coverage Gap Identification: Flags high-risk areas lacking adequate testing.
  • Anti-Test List: Explicitly defines what should not be tested to save resources.
  • Use Case: Before starting development on a new, complex microservice, use this Skill to define a comprehensive test plan that balances thoroughness with development speed.

Quick Start

Use the plan-test-strategy skill to produce a test strategy for the new user authentication module.

Frequently Asked Questions about plan-test-strategy

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

FAQPage Schema
How do I create a test strategy that balances code coverage with maintenance cost?

A test strategy balances coverage and maintenance cost by assessing feature risk to recommend optimal test layers, identifying brittleness risks, and explicitly defining what not to test. This optimizes reliability gain while minimizing unnecessary effort.

What is the best way to determine which test layer to use for a new software feature?

Determining the test layer involves analyzing the feature's blast radius, change frequency, failure cost, and complexity. This risk assessment recommends the lowest effective testing layer, such as unit or integration, with clear rationale.

How do I identify brittle tests before they break during implementation changes?

Identifying brittle tests requires analyzing the proposed test strategy for implementation coupling. The analysis flags tests prone to breaking due to code changes and suggests mitigations to improve overall test reliability.

How do I assess the risk of untested coverage gaps in a complex component?

Assessing coverage gap risk involves evaluating the component's external coupling and failure cost. The analysis flags high-risk areas lacking adequate testing to ensure critical aspects receive appropriate test investment.

When should I explicitly define an anti-test list for my software quality assurance process?

An anti-test list should be defined when optimizing test investment for complex features. Explicitly listing what not to test saves resources, avoids unnecessary effort, and maintains development speed without sacrificing reliability.