Skip to content
Skills Library
Programming · Planning

test-plan

/test-plan

Create a full test plan or test strategy document for a feature, release, or project. Use when the user asks for a test plan, test strategy, or QA planning for a release.

Licence
MIT
Last repository change
31.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create a full test plan or test strategy document for a feature, release, or project. Use when the user asks for a test plan, test strategy, or QA planning for a release.

Original author description

Create a full test plan or test strategy document for a feature, release, or project. Use when the user asks for a test plan, test strategy, or QA planning for a release.

How it works

  1. Document structure
Original SKILL.md headings · 20 lines, 191 words
SKILL.md preview
---
name: test-plan
description: Create a full test plan or test strategy document for a feature, release, or project. Use when the user asks for a test plan, test strategy, or QA planning for a release.
---

# Test Plan Builder

Create a practical test plan document. Ask the user first (briefly, max 3 questions) about: what is being tested, the deadline/timeline, and the team size — unless they already said.

## Document structure

Write the plan as a markdown file in the project (e.g. `test-plans/<feature>-test-plan.md`) with these sections:

1. **Overview** — what is being tested, in 2-3 sentences
2. **Scope** — In scope / Out of scope (explicit lists)
3. **Test Approach** — which test types apply: functional, regression, API, UI, cross-browser/device, performance, security, accessibility. For each, say *why* it applies or is skipped.
4. **Entry / Exit Criteria** — when testing starts, when it's done (e.g. "all P1/P2 defects fixed, 95% test cases executed")
5. **Test Environment & Data** — environments, accounts, test data needs
6. **Risks & Mitigations** — realistic risks (tight timeline, unstable environment, missing requirements)
7. **Schedule & Estimates** — rough phases with effort
8. **Deliverables** — test cases, defect reports, summary report

Keep it lean — a plan people will actually read (1-2 pages), not a 20-page template. Mark anything you assumed with `(assumption)` so the tester can confirm with the team.

Versions

RepositoryScoreLicence
This page · MohamedRamadanSalah/claude-qa-toolkit90MIT
LeMarkk/agent-skills100MIT
ghassenazzouz/claude-qa-agent100MIT
omexit/claude-skills-pack100MIT
katalon-labs/true-skills100MIT
yasunori0418/skills90MIT

Database snapshot: 13.11.2026 · package version 0fbafb845754 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-test-plan
    Create a test plan when the user asks to plan testing, define test cases, create a QA strategy, write a test plan, or prepare for testing a feature
  • 100proof-strategy
    Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
  • 100test-strategy-author
    Authors a test strategy document (a master test plan) for a project, release, or feature - covers scope, in/out, test types per layer (unit / integration / contract / E2E / perf / security / a11y), risk-based test prioritization that maps top risks to test investment (per…
  • 90qa-ticket-prep
    Use when preparing a test plan for a software release. Triggered by phrases like "create test plan for X release", "generate test cases for these changes", "what should we test for version X", or when given a milestone, version number, or Jira release ticket.
  • 10001-test-strategy
    Use when producing or updating project test strategy for risk-based test levels, test types, environments, tooling, entry criteria, and exit criteria. Use test-plan for the neighbouring concern; this skill owns the named document contract and its acceptance evidence.
  • 100qa-strategy
    Create QA test strategy documents, coverage matrices, and risk-based test prioritization plans. Use this skill whenever a QA lead or manager needs to plan what to test, why, and at what depth. Trigger on phrases like "write a test strategy", "test strategy document", "what…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.