Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates; triggers include test strategy and QA planning.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Test Strategy
**Chinese version：** See the corresponding Chinese skill.
## When to Use
- Need help with test strategy in a real project context.
- Need an output that can be used directly for execution, review, or follow-up.
## Workflow
1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
4. Default to Markdown; switch formats only when the user asks.
## Core Constraints
- Prioritize by risk / business impact — do not treat everything equally.
- Separate confirmed facts from current assumptions.
- Do not invent endpoints, fields, environments, or root causes the user did not provide.
- Keep output executable: concrete scenarios, clear priority, clear next steps.
## Progressive Disclosure
- Before producing output, read and follow `prompts/test-strategy.md` (minimum coverage, output structure, quality bar).
- When Excel/CSV/JSON/Word is requested: read `output-formats.md` and honor the format.
…
The line at the top of this page pins the label git:20260903.6713296, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2532 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
naodeng/awesome-qa-skills · 279 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dzkaiwhjsy4awn7i
GET https://markdownregistry.com/api/v1/resolve?ref=naodeng/awesome-qa-skills/test-strategy
GET https://markdownregistry.com/api/v1/blob/4cc2317add104ddd41489babdb03b9439923134552fe3c7dac6488fb1c4b42ee
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/calibration/SKILL.md · Offline answer fixtures for calibrating an experimental semantic judge; not a Pilot Skill or runtime result.
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/functional-testing-en/SKILL.md · Use this skill when you need to design functional test plans or cases for business flows, UI, data, and integrations…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/functional-testing-zh/SKILL.md · Use this skill when you need to design functional test plans or cases for business flows, UI, data, and integrations…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/performance-testing-en/SKILL.md · Use this skill when you need to design performance testing for load, stress, spike, endurance, or capacity objectives…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/performance-testing-zh/SKILL.md · Use this skill when you need to design performance testing for load, stress, spike, endurance, or capacity objectives…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/skill-change-verification-en/SKILL.md · Use this skill when selecting and reporting verification for Skill changes; triggers include Skill change verification…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/skill-change-verification-zh/SKILL.md · Use this skill when selecting and reporting verification for Skill changes; triggers include Skill 变更验证、质量门禁、evidence…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/skill-evaluation-en/SKILL.md · Use this skill when designing, running, interpreting, or reporting Agent Skill evaluations, selecting cases or judges…
naodeng/awesome-qa-skills · evidence/skill-quality/2026-10-03-codex-pilot/reproduction/packages/skill-evaluation-zh/SKILL.md · Use this skill when designing, running, interpreting, or reporting Agent Skill evaluations, selecting cases or judges…
nahid-sparktales/agent-dispatcher · skills/quality/test-strategy/SKILL.md · Decide what to test and at which level before any tests get written — enumerate failure modes by consequence, give each…
fishzjp/qa-skills · skills/test-strategy/SKILL.md · "How should this be tested?" Evidence-backed risk map → scope and depth across functional domains and 10 testing-type…
aethrox/doctrine · skills/test-strategy/SKILL.md · Suite-level testing decisions that sit above individual tests, where test data comes from (synthetic factories vs…
jpantsjoha/ai-native-developer-experience · skills/test-strategy/SKILL.md · Map requirement acceptance to proportionate executable checks and real user journeys before implementation and…
frnkgns/gentjinskills · skills/test-strategy/SKILL.md · Decide what should be tested, at which seam, and at which level before or during implementation. Use when implementing…
aks-builds/quality-skills · skills/test-strategy/SKILL.md · When the user wants to design, audit, or evolve a test strategy — the shape of their test pyramid, the balance of unit…
marielynneblock/arcanum-artifex · skills/development/test-strategy/SKILL.md · Produces a test strategy document defining what to test, at which layer, with which tools, and to what coverage…
