Borrowing it
Nothing to install: this file belongs to nurettincoban/ai-prd-workflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nurettincoban/ai-prd-workflow/main/.claude/commands/test-strategy.mdgit clone --depth 1 https://github.com/nurettincoban/ai-prd-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/test-strategy)<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/test-strategy"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/test-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nurettincoban/ai-prd-workflow/test-strategy"><img src="https://agentmods.dev/badge/commands/nurettincoban/ai-prd-workflow/test-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.01055 |
| Opus 5 | $0.00005 | $0.00528 |
| Sonnet 5 | $0.00002 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
test-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
- 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.
SCOPE THE CHECKLIST TO THE PRODUCT TYPE
First classify the product: web app · mobile app · library/SDK · CLI · service/API · data pipeline · game.
Apply only the sections and checks that fit that type. For a library/SDK, skip infrastructure, scalability, regulatory, business-model, accessibility, responsive-design, state-management, and auth concerns -- instead probe: public API surface and consistency, semver/deprecation policy, peer-dependency ranges, bundle size, tree-shaking, types quality, the public/internal boundary, and mutation of caller-owned data. Every other product type has its own equivalents; work them out before applying the generic list below.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 91 lines · 9 tokens per session scan A 220a78d3191c
test-strategy is a command published in the GitHub repository nurettincoban/ai-prd-workflow (285 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,055 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
fest-validate
Validate festival structure and find issues.
lfe-tdd
Red-green-refactor quality pass on code the Builder just wrote. Use in the Builder sub-pipeline after lfe-builder completes implementation.
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.
enhance-prompt
Command "enhance-prompt" from VoDaiLocz/Enhance-Prompt, covering enhance prompt workflow, 1. intake and scoring (enhance-prompt/skill.md), 5. ambiguity check and 8. iteration (enhance-prompt/references/iteration-mode.md).
lfe-mutation-verify
Inspector sub-skill. Prompt-based mutation testing — reasons about whether existing tests would catch hypothetical code mutations. No test runner required. Writes .plans/checks/mutationfindings.md. Called by lfe-inspector when enabled in inspector-config.md. Enable only for critical or safety-sensitive modules.
paul:verify
Guide manual user acceptance testing of recently built features.