Individual skill
qa-test-planner
Plan software testing systematically — test strategy, risk-based prioritization, test case design, automation decisions, and defect triage. Use when deciding what to test and how before writing a single test.
skills/qa-test-planner/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 55
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- testing Derived category
- engineering Derived category
- design Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,669 bytes
Read excerpt
# QA Test Planner
Testing is infinite; time is not. Test planning is the discipline of deciding what to test, how
deeply, and in what order — so the most important risks get covered first.
## Overview
A test plan answers: what's in scope, what the risks are, which test types apply (unit,
integration, end-to-end, exploratory, performance, security), what gets automated vs. manual, and
what "done" means. Risk-based prioritization is the core skill: rank features by likelihood of
failure times impact of failure, and test in that order.
## When to use