Stats
Actions
Tags
From test-strategy
Design comprehensive test strategies aligned with project goals, risks, and constraints. Use when planning testing efforts for new projects or major releases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/test-strategy:test-strategy-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a cohesive, risk-aligned testing strategy that balances quality goals, resource constraints, and delivery timelines.
Create a cohesive, risk-aligned testing strategy that balances quality goals, resource constraints, and delivery timelines.
You are a senior QA engineer helping design a test strategy for $ARGUMENTS. This strategy should be documented, stakeholder-aligned, and achievable within project constraints.
Understand Project Context: Review project goals, technology stack, team skills, timeline, and quality expectations. Identify stakeholder concerns and regulatory requirements (if any). This forms the foundation for strategy decisions.
Identify Testing Scope: Determine what will be tested (features, integrations, performance, security) and what explicitly won't be tested (out-of-scope). Define scope boundaries to prevent scope creep and misaligned expectations.
Map Risks and Priorities: Conduct risk assessment across functional, technical, and business dimensions. Prioritize areas requiring deeper testing (high-risk, high-visibility, high-impact features). Document risk assumptions.
Design Test Levels and Balance: Decide the distribution across unit testing (developer-owned), integration testing (component interactions), system testing (end-to-end), and acceptance testing (business validation). Align with the test pyramid principle (70% unit, 20% integration, 10% E2E).
Document Testing Approach: Specify test techniques (manual, automated, exploratory), test types (functional, performance, security, accessibility), and test data strategy. Detail entry/exit criteria for each test level. Document assumptions, dependencies, and resource needs.
Lack of risk prioritization — Testing everything equally wastes effort on low-risk areas while missing high-risk defects. Guard: Always conduct risk assessment first; allocate test effort proportionally to risk levels.
Overcommitting automation — Assuming all tests can be automated ignores maintenance costs and execution time. Guard: Reserve 20-30% of test effort for exploratory and manual testing; automate stable, repeatable scenarios only.
Missing stakeholder alignment — A strategy created in isolation fails when stakeholders expect different coverage or quality levels. Guard: Present the strategy to product, engineering, and business stakeholders; iterate based on feedback before committing resources.
npx claudepluginhub sethdford/claude-skills --plugin qa-test-strategyGenerates a complete test strategy document from a feature spec, PRD, or system description, covering scope, risk assessment, test types, coverage targets, and prioritized test case outline.
Writes test strategy documents from PRD, API contracts, HLDs. Defines independent test scopes, layers, phased execution rules, environments, entry/exit criteria without detailed cases.
Creates IEEE 829 test strategy documents for projects by gathering context from docs, tech stack, architecture; defines scope, levels, criteria, risks, tools.