Map requirement acceptance to proportionate executable checks and real user journeys before implementation and completion.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Test Strategy
Read the accepted requirement, relevant business journey, risks and project check
commands. Maintain the existing test strategy with criterion → check → environment →
owner mappings; identify uncovered criteria before dispatch.
Choose unit checks for logic, integration checks for seams, and journey checks for the
actual user entrypoint. Include relevant negative, persistence, permission, recovery and
regression cases. A direct API call cannot substitute for a changed browser interaction;
a health response cannot establish user acceptance. Use owned manual checks when
appropriate and report their result separately from automated coverage.
For planning-only assignments, return the coverage map and commands to the assigned
worker; do not execute or create fixtures. When execution is authorised within your lane,
run candidate checks and record command, revision, environment, outcome and limits. For new regression guards verify a representative defect makes the check fail
in an isolated fixture; do not damage a shared working tree. Avoid tests that merely
repeat wording or implementation. Return uncovered acceptance to product-owner and
…
The line at the top of this page pins the label git:20261016.e93069b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_jg2s65ieaaw6qwje
GET https://markdownregistry.com/api/v1/resolve?ref=jpantsjoha/ai-native-developer-experience/test-strategy
GET https://markdownregistry.com/api/v1/blob/1cd651374ca8095216ee5c14ac542570ccff9a825b14b79afeaff7737e82da18
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jpantsjoha/ai-native-developer-experience · skills/adversarial-gate/SKILL.md · JP's signature red-team pass — "how would I break this?" Argue against your own approach before proceeding. Trigger on…
jpantsjoha/ai-native-developer-experience · skills/cloud-checkup/SKILL.md · Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud…
jpantsjoha/ai-native-developer-experience · skills/cost-guardrail/SKILL.md · LLM and cloud cost awareness — model tiering, token budgets, right-sizing, and when a cheaper model suffices. Trigger…
jpantsjoha/ai-native-developer-experience · skills/cxo-oversight/SKILL.md · Challenge vision alignment, value, cost, risk and operating ownership at material scope or release decisions.
jpantsjoha/ai-native-developer-experience · skills/delivery-orchestrator/SKILL.md · Decompose an epic into atomic parallelizable tasks, route each to the right skill, and keep the four delivery records…
jpantsjoha/ai-native-developer-experience · skills/domain-validator/SKILL.md · Validate agent output against declared domain rules and ground truth before trusting it downstream. Trigger after any…
jpantsjoha/ai-native-developer-experience · skills/get-it-done/SKILL.md · Pursue an agreed goal to a working outcome without waiting: decompose it, re-prioritise as evidence arrives, branch…
naodeng/awesome-qa-skills · skills/en/testing-types/test-strategy/SKILL.md · Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates…
nahid-sparktales/agent-dispatcher · skills/quality/test-strategy/SKILL.md · Decide what to test and at which level before any tests get written — enumerate failure modes by consequence, give each…
fishzjp/qa-skills · skills/test-strategy/SKILL.md · "How should this be tested?" Evidence-backed risk map → scope and depth across functional domains and 10 testing-type…
aethrox/doctrine · skills/test-strategy/SKILL.md · Suite-level testing decisions that sit above individual tests, where test data comes from (synthetic factories vs…
frnkgns/gentjinskills · skills/test-strategy/SKILL.md · Decide what should be tested, at which seam, and at which level before or during implementation. Use when implementing…
aks-builds/quality-skills · skills/test-strategy/SKILL.md · When the user wants to design, audit, or evolve a test strategy — the shape of their test pyramid, the balance of unit…
marielynneblock/arcanum-artifex · skills/development/test-strategy/SKILL.md · Produces a test strategy document defining what to test, at which layer, with which tools, and to what coverage…
