QA & Auditing

Testing Strategy

Creates risk-based testing strategy across unit, integration, end-to-end, accessibility, visual and performance layers.

What it does

Creates risk-based testing strategy across unit, integration, end-to-end, accessibility, visual and performance layers.

When to use it

Use when defining acceptance criteria, test layers, release evidence, or fixing flaky, unreliable test coverage.

Problems it prevents

Stops testing effort spent evenly everywhere instead of concentrated on the areas real risk lives in.

Typical workflow

  1. Establish risk and scope
  2. Design the right test layers
  3. Control environments and test data
  4. Build a release evidence matrix

Example output

A test plan where coverage depth is explicitly justified by risk, with a release evidence matrix, not just a pass/fail badge.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/testing-strategy/ to use it on every project, or in .claude/skills/testing-strategy/ to scope it to one repository. Then invoke it directly:

/testing-strategy

Read the official Claude Code skills guide

Works well with