Test Strategy Doc
mohitagw15856/pm-claude-skills
Write a test strategy document from a feature spec, PRD, or system description.
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
Install Test Strategy
$ npx skills add nurettincoban/ai-prd-workflow --skill test-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nurettincoban/ai-prd-workflow test-strategy --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/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-strategy .claude/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .claude/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategyType 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 nurettincoban/ai-prd-workflow --skill test-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nurettincoban/ai-prd-workflow test-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-strategy .agents/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .agents/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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 nurettincoban/ai-prd-workflow --skill test-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nurettincoban/ai-prd-workflow test-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-strategy .cursor/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .cursor/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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/nurettincoban/ai-prd-workflow.git --path skills/test-strategy--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 nurettincoban/ai-prd-workflow --skill test-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nurettincoban/ai-prd-workflow test-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-strategy .gemini/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .gemini/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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 nurettincoban/ai-prd-workflow test-strategyInstalls 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 nurettincoban/ai-prd-workflow --skill test-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-strategy .github/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .github/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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 nurettincoban/ai-prd-workflow --skill test-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nurettincoban/ai-prd-workflow test-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-strategy .opencode/skills/test-strategy && 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" agent skill from https://github.com/nurettincoban/ai-prd-workflow/tree/main/skills/test-strategy into .opencode/skills/test-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-strategy", 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- GitHub stars
- 298
- Token cost
- ~1.4k tokens
- SKILL.md length
- 763 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
- Tasks that involve Test generation
- SKILL.md covers Inputs, WHEN ARTIFACTS CONFLICT, STEP 0: ESTABLISH THE BASELINE and PRODUCT TYPE, plus 3 more sections
- Runs Python scripts from its folder; calls python3
- Tasks that involve Test strategy
What it does
Test Strategy is an agent skill from nurettincoban/ai-prd-workflow. Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/trace-check.py`).
It sits in Testing & QA, covering Test generation, Test strategy and PRD writing. The repository describes itself as: RFC-driven development for AI coding agents: idea or existing codebase → verified PRD → features → rules → sequenced RFCs → reviewed code. Agent Skills for Claude Code, Codex… The licence is MIT.
When your agent uses it
- Tasks that involve Test generation
- Tasks that involve Test strategy
- Tasks that involve PRD writing
Example prompts
- “/test-strategy”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit b67f4d3. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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 loads about 1.4k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 763 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); the scripts in this folder are not scanned.
SKILL.md
The full file from nurettincoban/ai-prd-workflow at commit b67f4d3, republished under its MIT licence (© nurettincoban). 763 words, ~1,427 tokens.
Download SKILL.mdSave it as
.claude/skills/test-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- test-strategy
- description
- Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
- metadata.source
- https://github.com/nurettincoban/ai-prd-workflow
- metadata.version
- 3.0.0
- metadata.checksum
- sha256:cd55d1f014fc3d0bd93b5bd69c7b6db301a767ccda34f1818b65bd64f785890c
You are an expert QA engineer and test architect tasked with generating a comprehensive test plan based on the project's features and RFCs.
Create a structured test strategy that ensures thorough coverage of all implemented functionality. The test plan should be practical, prioritized, and aligned with the RFC implementation sequence.
Inputs
- PRD.md for the Product Type section
- FEATURES.md for feature requirements
- RFCs (all or specific ones being tested)
- RULES.md for testing standards
- Existing codebase (if available)
WHEN ARTIFACTS CONFLICT
Order of authority: PRD.md > FEATURES.md > RULES.md > RFCs > generated plans. Where this prompt's generic guidance conflicts with RULES.md, RULES.md wins -- it was written for this project and this prompt was not. Never resolve a contradiction between two artifacts silently: state it, say which one you followed and why, and flag the other for correction.
STEP 0: ESTABLISH THE BASELINE
Before planning anything, run the existing test suite and report the actual baseline: how many tests exist, which files they live in, and what passes or fails. Paste the real output.
Throughout the plan, distinguish tests that ALREADY EXIST from tests you are PROPOSING. Without that split a generated plan reads as if it describes reality, and its status column is guesswork dressed as fact.
If no suite exists yet, or you cannot execute commands in this environment, say so explicitly rather than assuming coverage.
PRODUCT TYPE
Read the Product Type section of PRD.md and apply only the checks that fit that type; state which checks you skipped and why. Skipping must be visible, never silent. If PRD.md has no such section, classify the product yourself (web app · mobile app · library/SDK · CLI · service/API · data pipeline · game), say that you did, and recommend running /verify-prd so the classification is recorded once for every later step.
Test Plan Sections
Replace sections that do not fit the product type rather than padding them. For a library of pure functions, most of sections 2-6 do not apply; the useful equivalents are numeric correctness, immutability of caller-owned data, determinism, API surface, bundle size, and supply chain.
1. UNIT TESTING
- Identify key functions and modules requiring unit tests
- Specify edge cases and boundary conditions for each
- Define mock/stub strategy for external dependencies
- Identify logic that requires exhaustive coverage. If RULES.md defines a coverage policy, follow it rather than imposing a percentage of your own
2. INTEGRATION TESTING
- API endpoint testing (request/response validation, error codes)
- Database interaction testing (CRUD operations, migrations, constraints)
- Third-party service integration testing
- Inter-component communication verification
3. END-TO-END TESTING
- Critical user journey test scenarios (happy path and error paths)
- Cross-browser and cross-device considerations
- Authentication and authorization flow testing
- Data flow verification from input to persistence
4. SECURITY TESTING
- Authentication and authorization boundary testing
- Input validation and injection testing (SQL, XSS, CSRF)
- Data privacy verification (PII handling, encryption)
- Rate limiting and abuse prevention testing
Show full SKILL.md (297 more words)Show less
5. PERFORMANCE TESTING
- Load testing scenarios with expected thresholds
- Response time benchmarks for critical endpoints
- Resource utilization limits (memory, CPU, connections)
- Stress testing for degradation behavior
6. TEST DATA STRATEGY
- Test data generation approach (factories, fixtures, seeds)
- Database state management between test runs
- Sensitive data handling in test environments
- Data cleanup procedures
Output Format
For each RFC/feature, provide:
- Test cases with clear descriptions and steps
- Priority (Must have / Should have / Could have) -- taken from the feature's existing MoSCoW rating in FEATURES.md, not reassigned here
- Expected results and failure criteria
- Prerequisites and dependencies
Provide a test execution order that aligns with the RFC implementation sequence. Highlight any testing gaps where manual testing may be needed.
Save the plan to TEST-STRATEGY.md, with one section per RFC headed ## RFC-[ID]: [title], so /implement-rfc and /review-rfc can find the tests planned for the RFC in front of them. If TEST-STRATEGY.md already exists, update it in place: keep the sections of RFCs that are already implemented, and mark changed plans rather than silently rewriting them.
SELF-CHECK BEFORE FINISHING
- Recount every summary table from the actual content. Never carry a count forward from earlier in your own output.
- Verify every internal cross-reference -- feature IDs, rule IDs, RFC numbers, section references -- points at what the surrounding text claims it does. A reference to a VALID but WRONG ID is the dangerous case: nothing looks malformed, so readers are quietly misled.
- Confirm no two tables in the document disagree with each other.
- If
trace-check.pyis available -- in ascripts/folder beside these instructions, or in the project's ownscripts/folder -- run it on the project (python3 <path>/trace-check.py .) and fix every FAIL it reports. It checks IDs, coverage and dependencies mechanically, which reading cannot do reliably. - State that you ran this check and what it turned up.
© nurettincoban, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in skills/test-strategy of nurettincoban/ai-prd-workflow.
- SKILL.md
- scripts/trace-check.py
Open the folder on GitHubat commit b67f4d3
Compare with similar skills
Test Strategy 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 this skillnurettincoban/ai-prd-workflow | 298 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Test Strategy Docmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | 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 nurettincoban/ai-prd-workflow
All 11 skills in this repoGenerate Rfcs
nurettincoban/ai-prd-workflow
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
Workflow Status
nurettincoban/ai-prd-workflow
Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.
Document Existing
nurettincoban/ai-prd-workflow
Document an existing codebase as PRD.md, FEATURES.md and RULES.md, so new work is planned against the code as it is.
Generate Rules
nurettincoban/ai-prd-workflow
Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule IDs.
Verify Prd
nurettincoban/ai-prd-workflow
Review PRD.md for gaps, contradictions and unverifiable claims, write an improved PRD.md and record the findings in PRD-REVIEW.md.
Extract Features
nurettincoban/ai-prd-workflow
Turn PRD.md into FEATURES.md: permanent feature IDs, MoSCoW priorities, acceptance criteria and the PRD requirement each feature comes from.
Related
Categories
Questions about Test Strategy
What does Test Strategy do?
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written. Test Strategy is an agent skill from nurettincoban/ai-prd-workflow.md, a test plan per RFC, before the tests are written.
When should I use Test Strategy?
Test Strategy fits situations like: tasks that involve Test generation; tasks that involve Test strategy; tasks that involve PRD writing.
How do I install Test Strategy in Claude Code?
Run `npx skills add nurettincoban/ai-prd-workflow --skill test-strategy -a claude-code`. Or copy the skill folder (skills/test-strategy in nurettincoban/ai-prd-workflow) into .claude/skills/test-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Test Strategy in Codex?
Run `npx skills add nurettincoban/ai-prd-workflow --skill test-strategy -a codex`. Or copy the skill folder (skills/test-strategy in nurettincoban/ai-prd-workflow) into .agents/skills/test-strategy in your project. Codex loads it when a task matches its description.
Can I use Test Strategy 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 nurettincoban/ai-prd-workflow --skill test-strategy -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, .gemini/skills/test-strategy, .github/skills/test-strategy and .opencode/skills/test-strategy in your project.
What does Test Strategy need to run?
Going by SKILL.md and its folder, Test Strategy needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Test Strategy 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 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Test Strategy use?
Test Strategy 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 use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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?
Skills that share tags, products or a category with Test Strategy: Test Strategy Doc (mohitagw15856/pm-claude-skills, 1.4k 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?
nurettincoban (a GitHub user) maintains it in nurettincoban/ai-prd-workflow, which has 298 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.
Source: nurettincoban/ai-prd-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.