Test Strategy
nurettincoban/ai-prd-workflow
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
Write a test strategy document from a feature spec, PRD, or system description.
Install Test Strategy Doc
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-doc --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-strategy-doc .claude/skills/test-strategy-doc && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .claude/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-docType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-doc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-strategy-doc .agents/skills/test-strategy-doc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .agents/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-doc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-strategy-doc .cursor/skills/test-strategy-doc && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .cursor/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/test-strategy-doc--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-doc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-strategy-doc .gemini/skills/test-strategy-doc && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .gemini/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-docInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-strategy-doc .github/skills/test-strategy-doc && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .github/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills test-strategy-doc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-strategy-doc .opencode/skills/test-strategy-doc && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "test-strategy-doc" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/test-strategy-doc into .opencode/skills/test-strategy-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy-doc", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
test-strategy-doc- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 848 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a test strategy document from a feature spec, PRD, or system description.
- Works in 6 steps: Test Scope → Risk Assessment → Test Types and Coverage → …
- Asked to create a test plan
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Strategy Doc is an agent skill from mohitagw15856/pm-claude-skills. Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing for a feature or release. Produces a complete test strategy with scope, risk assessment, test types, coverage targets, and a prioritised test case outline.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test strategy, Test generation and PRD writing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to create a test plan
- Write a test strategy
- Define QA approach
- Plan testing for a feature
Example prompts
- “/test-strategy-doc”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Test Strategy Doc loads about 1.6k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 848 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 848 words, ~1,636 tokens.
Download SKILL.mdSave it as
.claude/skills/test-strategy-doc/SKILL.md (or your agent's skills folder).- name
- test-strategy-doc
- description
- Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing for a feature or release. Produces a complete test strategy with scope, risk assessment, test types, coverage targets, and a prioritised test case outline.
Test Strategy Document Skill
Produces a complete test strategy from a feature spec, PRD, or system description — covering scope, test types, risk areas, coverage requirements, and a prioritised test case outline.
Required Inputs
Ask for these if not provided:
- Feature or system being tested (paste a spec, PRD, or describe it in plain English)
- Tech stack (language and framework — e.g. TypeScript + React, Python + FastAPI)
- Existing test coverage (e.g. "we have unit tests but no E2E tests", "we use Jest + Playwright already", or "starting from scratch")
- Deployment cadence (e.g. continuous deployment / weekly releases / quarterly — affects what must be automated vs. manual)
- Risk level (low / medium / high / critical — affects depth and coverage requirements)
- Timeline (when does this need to ship — affects prioritisation)
- Team context (who is doing the testing — developers / dedicated QA / both)
Output Format
1. Test Scope
In scope:
- [Specific functionality being tested]
- [Integration points covered]
- [User-facing flows included]
Out of scope:
- [What is deliberately not tested here — and why]
- [Dependencies owned by other teams]
Assumptions:
- [What the test strategy assumes is true — e.g. mocked services, test data availability]
2. Risk Assessment
Identify the highest-risk areas first — these drive depth and coverage:
| Area | Risk Level | Why | Test Priority |
|---|---|---|---|
| [e.g. Payment processing] | High | Money movement, regulatory | P0 — exhaustive |
| [e.g. User authentication] | High | Security boundary | P0 — exhaustive |
| [e.g. Email notifications] | Medium | External dependency | P1 — happy path + key failures |
| [e.g. UI copy changes] | Low | Visual only, reversible | P2 — smoke only |
3. Test Types and Coverage
Unit Tests
- What: Individual functions and methods in isolation
- Who writes: Developer
- Coverage target: [e.g. 80% line coverage on new code / 100% on critical paths]
- Tools: [e.g. Jest, pytest, go test]
- Focus areas for this feature: [Specific logic that needs unit coverage]
Integration Tests
- What: Service interactions, database operations, API contracts
- Who writes: Developer / QA
- Coverage target: [All happy paths + key failure modes]
- Tools: [e.g. Supertest, pytest + testcontainers]
- Focus areas: [Specific integrations at risk — e.g. third-party API, DB schema changes]
End-to-End Tests
- What: Critical user journeys from browser/client to database
- Who writes: QA / Developer
- Coverage target: [Top N user journeys — list them]
- Tools: [e.g. Playwright, Cypress, Selenium]
- Focus areas: [The 3–5 most critical user flows]
Performance Tests (include if any row in the Risk Assessment table has performance as a risk factor, regardless of overall risk level)
- What: Load, stress, or latency testing
- Targets: [Specific numbers — e.g. 200 req/sec at p95 < 200ms]
- Tools: [e.g. k6, Locust, JMeter]
Security Tests (include only if risk is high+)
- What: OWASP Top 10 checks relevant to this feature
- Focus: [Auth bypasses, injection, data exposure]
- Tools: [e.g. OWASP ZAP, manual penetration testing, Snyk]
4. Test Case Outline
Priority-ordered list of specific test cases:
P0 — Must pass before merge:
| Test Case | Type | Expected Outcome |
|---|---|---|
| [e.g. User can log in with valid credentials] | E2E | [Redirect to dashboard, session created] |
| [e.g. Invalid login returns 401] | Integration | [Error message displayed, no session] |
| [e.g. Password is never stored in plain text] | Unit | [bcrypt hash in DB] |
P1 — Must pass before release:
| Test Case | Type | Expected Outcome |
|---|---|---|
| [e.g. Login fails gracefully when DB is down] | Integration | [User sees friendly error, 503] |
| [e.g. Rate limiting blocks after 5 failed attempts] | Integration | [429 returned, account flagged] |
P2 — Should pass, can ship with known issues tracked:
| Test Case | Type | Expected Outcome |
|---|---|---|
| [e.g. Login page renders correctly on mobile] | E2E | [Layout matches design] |
Show full SKILL.md (299 more words)Show less
5. Test Data Requirements
- [Specific test data needed — e.g. test user accounts with various states]
- [External service stubs or mocks needed]
- [Database seed data requirements]
- [Any PII concerns and how test data handles them]
6. Definition of Done
Testing is complete when:
- All P0 test cases pass
- All P1 test cases pass
- Code coverage meets the stated target
- No critical or high severity bugs open
- Performance targets met (if applicable)
- Security checks completed (if applicable)
Quality Checks
- Risk table is populated and drives test priority (not filled in generically)
- Every "P0 — exhaustive" row in the Risk Assessment table has at least one corresponding P0 test case
- "Out of scope" section names at least one explicit exclusion (not left blank)
- Each test type names a concrete tool (not "some testing framework")
- Definition of Done is measurable (not "tests are done when QA is happy")
Anti-Patterns
- Do not write a test strategy without a risk table that drives test priority — generic coverage targets are not a strategy
- Do not leave the "out of scope" section blank — every test strategy must explicitly name what is not being tested and why
- Do not specify test types without naming a concrete tool for each — "some testing framework" is not actionable
- Do not define a Definition of Done that is not measurable — "QA is happy" is not a completion criterion
- Do not create P0 risk areas without corresponding P0 test cases — risk rating must map to test coverage
Usage Examples
- "Write a test strategy for [feature]" + [paste spec or PRD]
- "Create a test plan for [system]"
- "How should we test [feature]?"
- "I need a QA plan for this sprint"
- "What tests do we need for [X]?"
Example Trigger Phrases
- "Create a test plan."
- "Write a test strategy."
- "Define QA approach."
- "Plan testing for a feature."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/test-strategy-doc of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Test Strategy Doc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Test Strategy Doc this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Test Strategynurettincoban/ai-prd-workflow | 298 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Prd V07 Test Planningmattgierhart/PRD-driven-context-engineering | 180 | — | ~3.5k | Automated safety check: Notes | MIT | |
| Bmad Testarch Test Designbmad-code-org/bmad-method-test-architecture-enterprise | 105 | 3 repos | ~1.4k | Automated safety check: Pass | Custom licence | |
| Designing TestsCloudAI-X/opencode-workflow | 275 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Automated Test Planningtestdouble/han | 281 | — | ~6.7k | Automated safety check: Pass | MIT |
Similar skills
Prd V07 Test Planning
mattgierhart/PRD-driven-context-engineering
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution.
Bmad Testarch Test Design
bmad-code-org/bmad-method-test-architecture-enterprise
Create system-level or epic-level test plans. An agent skill from bmad-code-org/bmad-method-test-architecture-enterprise.
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
Automated Test Planning
testdouble/han
Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.
Bmad Tea Testarch Test Design
chenjackle45/SayIt
Create system-level or epic-level test plans. An agent skill from chenjackle45/SayIt.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Test Strategy Doc
What does Test Strategy Doc do?
Write a test strategy document from a feature spec, PRD, or system description. Test Strategy Doc is an agent skill from mohitagw15856/pm-claude-skills. Write a test strategy document from a feature spec, PRD, or system description.
When should I use Test Strategy Doc?
Test Strategy Doc fits situations like: asked to create a test plan; write a test strategy; define QA approach; plan testing for a feature.
How do I install Test Strategy Doc in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a claude-code`. Or copy the skill folder (skills/test-strategy-doc in mohitagw15856/pm-claude-skills) into .claude/skills/test-strategy-doc in your project. Claude Code loads it when a task matches its description.
How do I install Test Strategy Doc in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a codex`. Or copy the skill folder (skills/test-strategy-doc in mohitagw15856/pm-claude-skills) into .agents/skills/test-strategy-doc in your project. Codex loads it when a task matches its description.
Can I use Test Strategy Doc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-strategy-doc, .gemini/skills/test-strategy-doc, .github/skills/test-strategy-doc and .opencode/skills/test-strategy-doc in your project.
What does Test Strategy Doc need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Strategy Doc is instructions for the agent only. Our summary lists: Python 3.
Does Test Strategy Doc access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Test Strategy Doc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Test Strategy Doc use?
Test Strategy Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Strategy Doc use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Test Strategy Doc?
Skills that share tags, products or a category with Test Strategy Doc: Test Strategy (nurettincoban/ai-prd-workflow, 298 stars), Prd V07 Test Planning (mattgierhart/PRD-driven-context-engineering, 180 stars), Bmad Testarch Test Design (bmad-code-org/bmad-method-test-architecture-enterprise, 105 stars) and Designing Tests (CloudAI-X/opencode-workflow, 275 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Strategy Doc?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.