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]