test-strategy

Test Strategy

Chinese version： See the corresponding Chinese skill.

When to Use

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
Default to Markdown; switch formats only when the user asks.

Build a minimum executable table linking objective→obligation/scope→layer/depth→data/environment→resources/owner→entry/exit rule source→evidence/residual risk.
Reuse the project stack and actual capacity, protecting critical loss/authority obligations first. Each scenario needs business postconditions/evidence; insufficient resources expose unfinished work and minimal alternatives.
Gates come from the project. Missing thresholds remain open/UNKNOWN; never apply an automatic95% pass gate. Human risk acceptance cannot be replaced by a strategy draft.
Separate design, plan, actual runs, and acceptance. Include dependencies/blockers, changes, stop/reassessment triggers, and owners so another executor can take over.

Prioritize by risk / business impact — do not treat everything equally.
Separate confirmed facts from current assumptions.
Do not invent endpoints, fields, environments, or root causes the user did not provide.
Keep output executable: concrete scenarios, clear priority, clear next steps.

When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
Before producing output, read and follow prompts/test-strategy.md (minimum coverage, output structure, quality bar).
When Excel/CSV/JSON/Word is requested: read output-formats.md and honor the format.
When a ready-made template fits: use matching files under output-templates/.
For deep framework/troubleshoot/schema notes: read only the relevant file(s) under references/, do not load the whole directory.
For format conversion or helper checks: prefer existing scripts/ over reinventing.
For evaluating/regressing this skill: use evals/ with skill-up.

Followed the main prompt's output structure
Minimum coverage focus: goals and scope, quality risks, test types and depth, priority areas, resource and ownership needs, environment and data strategy, entry and exit thinking, automation direction, ... (details in main prompt)
Covered the minimum checklist, or explained omissions
High-risk items have explicit priority
Did not invent details the user did not provide
Assumptions and gaps are marked