test-strategy-plus

Test Strategy Enhanced Edition (Chinese Version)

English version: See the corresponding English skill.

When to Use

You need a more complete test strategy, including milestones, quality gates, and responsibility arrangements.
You need stronger planning and trade-off explanations than the basic version.

Script Capability Boundaries

Optional scripts/run_*.py only prepares parsed input materials or source candidates, outputs NOT_ASSESSED, does not call models, does not execute the main Prompt, and does not generate semantic conclusions, risk priorities, complete test cases, or approvals. Formal analysis is executed by the Agent according to the main Prompt; when you need to run scripts, first read references/script-contract.md。

Execution Flow

Read and follow the main prompt in "Load on Demand" (coverage checklist, output structure, quality requirements).
Direct materials such as requirements, analysis, technical, and plan documents can always be used independently; role reports with source_role are only optional combined inputs, and must not require additional installation of role Skills.
Only supplement project context that truly affects the result: scope, environment, constraints, risks, dependencies, expected outputs.
When information is incomplete, first provide a usable initial version, and explicitly mark assumptions and information gaps.
Default to Markdown; switch only when the user specifies another format.

Core Constraints

Prioritize by risk/business impact; do not spread effort evenly.
Write "confirmed facts" and "current assumptions" separately.
Do not fabricate interfaces, fields, environments, or root cause details that the user did not provide.
When using role reports, retain the source role, and separately record delivery constraints, quality facts/conclusions, and risk acceptance.
The project manager may provide scheduling, resources, dependencies, and action tracking, but this content cannot rewrite quality conclusions, test facts, or risk acceptance; only consume report content, and do not depend on internal files of role Skills.
Results must be actionable: scenarios specific, prioritized, and able to guide the next step.

Load on Demand

Before producing output, you must read and follow prompts/test-strategy-plus.md(minimum coverage checklist, output structure, quality requirements).
When you need to apply an existing template: read the matching template in output-templates/ , and do not invent a conflicting structure.
When the user wants examples or to benchmark against existing assets: read the relevant examples in examples/ .
When you need in-depth materials such as framework specifications, troubleshooting, or report schema: read only the files in references/ that are relevant to the current problem, and do not read through the entire directory.
When you need format conversion or auxiliary validation: prefer using the existing scripts in scripts/ , rather than rewriting them.
When you need to evaluate/regress this skill: use evals/, and validate and run with skill-up.

Pre-Delivery Self-Check

Has followed the output structure of the main prompt
Minimum coverage concerns: goals and scope, risk priorities, test methods and depth, resources and responsibility arrangements, milestones, quality gates, entry and exit considerations, environment and data strategy… (details are subject to the main prompt)
Has covered the minimum checklist, or indicated why items are omitted
High-risk items have clear priorities
Has not fabricated details that the user did not provide
Assumptions and information gaps are identified
The project manager's scheduling/resource/dependency constraints do not override quality conclusions or authorization to accept alternative risks
When using role reports, retain the source role; direct input can still be used independently, and no internal files of the role Skill are linked

Common Misconceptions

When neither the scope nor the context is clear, do not pretend that it is already fully usable.
Do not write all items as equally important.
Do not skip assumptions and information gaps.
Do not output long passages of vague theory unrelated to the current toolchain.