test-planning
Writes a test plan for a sprint, release, epic or feature: scope, risks, approach by level, regression scope, environments, owners and exit criteria. Use when the user says 'test plan' or asks 'what do we test this sprint'. Not for the long-term QA direction (use test-strategy).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- test-planning
- license
- Apache-2.0
- description
- Writes a test plan for a sprint, release, epic or feature: scope, risks, approach by level, regression scope, environments, owners and exit criteria. Use when the user says 'test plan' or asks 'what do we test this sprint'. Not for the long-term QA direction (use test-strategy).
- argument-hint
- [sprint, release, epic or feature]
03 SKILL.md 正文
test-planning
Objective
A test plan turns a strategy into work for one scope and one time box. It states what will be tested, how, by whom and when, and how the team knows that it is done. It is short enough to read in five minutes.
Context
- Read
.agents/qa-project-context.mdif it exists. Use it, and skip the questions that it answers. - If it does not exist, find the facts in the repository. Suggest
qa-project-contextonce. Do not stop the work for it. - Read the test strategy if one exists. The plan must follow it, or say where it differs.
Discovery questions
- Which items are in scope (stories, tickets, changes)? Which are out of scope?
- What is the date, and how much test time is there?
- Which items are high risk?
- Which environments and test data are available, and when?
- Who tests what?
Workflow
- Scope. List the items with their requirement IDs. Mark new, changed and removed behavior.
- Risks. Score each item by impact and likelihood (see
risk-based-testing). Name the top risks. - Approach for each item. The levels (unit, API, integration, contract, UI, exploratory, non-functional), the existing tests to update, and the new tests to add. Use
test-case-designerfor the detailed cases of high-risk items. - Regression scope. From the changed areas and their reach (see
change-impact), choose the existing suites to run. - Environments and data. What each test needs, and when it is ready.
- Schedule and owners. Tasks with an owner and a date. Put the high-risk items first.
- Entry criteria. For example: the build is green, the feature is deployed to the test environment, the test data exists.
- Exit criteria. For example: all high-risk items tested, no open critical or major defects, the regression suites green, the exploratory sessions done, the known risks accepted by the owner.
- Risks of the plan itself. Late delivery, a missing environment, unclear requirements, with a mitigation.
Output
## Test plan: <scope> (<dates>)
| Item | Req IDs | Risk | Levels | New / updated tests | Owner | Status |
|---|---|---|---|---|---|---|
Regression: <suites> Environments: <...> Data: <...>
Entry criteria: ...
Exit criteria: ...
Plan risks: ...
Anti-patterns
- Same depth for every item. Low-risk items get as much time as high-risk items.
- No exit criteria. Testing stops when the time is over, not when the evidence is enough.
- Regression by habit. The full suite runs, or nothing runs, without a link to the change.
Done when
- Each in-scope item has a risk, an approach, tests and an owner.
- The regression scope, environments, data, entry criteria and exit criteria are stated.
- The plan risks have mitigations.
Related skills
risk-based-testing: scores the items.test-case-designer: the detailed cases.change-impact: the regression scope.release-readiness: checks the exit criteria at the end.
04 同仓库更多 Skills
unit-testing
Writes, fixes or improves unit tests for rules, calculations, validation and state logic: arrange-act-assert, exact oracles, boundary sets, doubles only at boundaries, controlled clock and randomness. Use when the user says 'write unit tests', 'TDD this' or 'mock this dependency'. Not for HTTP endpoints (use api-testing).
ui-automation
Writes, fixes or structures browser end-to-end tests for critical journeys: role, label or test ID locators, auto-waiting assertions, API data setup, page objects, auth reuse and traces. Use when the user says 'UI test', 'end-to-end test' or 'our UI tests are brittle'. Not for business rules (use unit-testing).
testcase-reviewer
Reviews automated tests or manual test cases like a senior test architect: scores fidelity, oracles, assertion depth, edge cases and determinism, and finds tests that pass on wrong code. Use when the user says 'review my tests', 'test smells' or 'review AI-written tests'. Not for fault injection (use mutation-probe).
testability-review
Scores how testable a feature, module or design is before tests exist (seams for clock, randomness and network, hidden state, observability) and gives the smallest production change per blocker. Use when the user asks 'is this testable' or 'why is this hard to test'. Not for writing the tests (use unit-testing).
test-strategy
Writes a test strategy for a product, system or team: quality goals, test levels and their share, environments, data, automation scope, non-functional testing, metrics and a roadmap. Use when the user says 'test strategy' or 'QA strategy'. Not for one sprint or release plan (use test-planning).
test-runner
Finds how a project runs its tests, runs the right subset, and triages each failure as product bug, test defect, environment problem or flaky test, with evidence. Use when the user says 'run the tests' or asks 'which tests fail and why'. Not for pipeline design (use ci-cd-integration).