Test Strategy Document

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.

▶ Run it free in the Playground View SKILL.md ↗

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

What to give it

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

Related skills

Test Strategy Document is one of 174 open-source professional AI agent skills. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog