One-Page Test Strategy

中文版： See the corresponding Chinese skill.

When to Use

• A team needs a visual test strategy that is easy to discuss, share, and update.
• Business goals, quality risks, and test approaches need to fit on one page.
• The strategy should show early testing, built-in quality, and relevant post-release feedback.

If the user needs a full execution plan, detailed staffing, or test cases, use the existing full test-strategy capability; do not force those details onto this page.

Workflow

1. Read and follow prompts/one-page-test-strategy.md for input review, output structure, and quality criteria.
2. Extract goals, current phase, key risks, system characteristics, team capability, and constraints; separate facts, assumptions, and gaps.
3. Follow the prompt's required modules: guiding principle and goal, functionality/performance/security scope, test enablers and constraints (environment/data/tools/team), seven lifecycle stages, shift-left/right, test quadrants, lean test layers, and iteration/release feedback.
4. If context is incomplete, provide a discussable draft with assumptions and open questions; do not invent gates, facts, or owners.