test-strategy-doc
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.
npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- Required Inputs
- Output Format
- 1. Test Scope
- 2. Risk Assessment
- 3. Test Types and Coverage
- 4. Test Case Outline
- 5. Test Data Requirements
- 6. Definition of Done
- Quality Checks
- Anti-Patterns
- Usage Examples
What does the test-strategy-doc skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill test-strategy-doc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.