Test Planning
Build a single sprint or release test plan.
Use Edge to load the skill test-planning from petrkindlmann/qa-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the petrkindlmann public repository. Edge did not write or edit this skill.
What it does
- Build a single sprint or release test plan.
- Covers feature decomposition into testable scenarios, requirements-to-test coverage mapping, effort estimation by test type, prioritization matrices (risk × effort), resource allocation, and scheduling with buffers.
- Use when: "sprint test plan," "release test plan," "what to test this sprint," "test estimation," "coverage mapping." Not for: multi-quarter strategy : use `test-strategy`.
- Not for: ranking areas by risk : use `risk-based-testing`.
- Not for: the go/no-go decision itself : use `release-readiness`.
- Related: test-strategy, risk-based-testing, release-readiness.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Test Planning.
Related skills
Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview framew
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers,
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or te
Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-18
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-18
Creator, source & licencepetrkindlmann
From the petrkindlmann public repository. Edge did not write or edit this skill.
- Repository
- petrkindlmann/qa-skills
- Skill file
- View source at revision
- Revision
- b3bb61bd268b147476252c6ed5a0440c87b97441
- Package hash
- sha256:f9a6f21fffdcf95316df3214210035fc6279131dafcf4f735b225ac8c4894c2e
- Licence
- MIT
- Description
- Build a single sprint or release test plan. Covers feature decomposition into testable scenarios, requirements-to-test coverage mapping, effort estimation by test type, prioritization matrices (risk × effort), resource allocation, and scheduling with buffers. Use when: "sprint test plan," "release test plan," "what to test this sprint," "test estimation," "coverage mapping." Not for: multi-quarter strategy : use `test-strategy`. Not for: ranking areas by risk : use `risk-based-testing`. Not for: the go/no-go decision itself : use `release-readiness`. Related: test-strategy, risk-based-testing, release-readiness.
Quoted from the skill’s own description
Read skill files4 files
4 files, 28.4 KB at revision b3bb61bd268b.
Questions about Test Planning
What does Test Planning do?
Build a single sprint or release test plan. Published by petrkindlmann (petrkindlmann/qa-skills).
Is Test Planning safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 18, 2026). The Evidence tab shows the scan.
How do I use Test Planning in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
Similar skills

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow re…

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;`/page/<token>…

Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or…

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when draft…

Read and write Google Docs.

Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example test…

Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-the…