create-test-strategylisted

# Create Test Strategy ## Trigger Use when the user asks what to test, how to verify a feature, which test types are needed, how to reduce release risk, or to write E2E tests. ## When To Use - Before or after implementation. - Before release planning. - When risk profile or coverage expectations are unclear. - When a user journey needs an automated regression check. ## Verify Before You Specify A test strategy written only from reading code describes what the code appears to do. Where a real browser is available, look at the actual behaviour first: the gap between intended and actual is usually where the useful tests are. ```bash sh "${CLAUDE_PLUGIN_ROOT}/scripts/playwright_cli.sh" open http://localhost:3000 --headed sh "${CLAUDE_PLUGIN_ROOT}/scripts/playwright_cli.sh" snapshot ``` On Windows use `scripts/playwright_cli.ps1`. Both wrap `npx --package @playwright/cli playwright-cli`, so no global install is needed; they fail with a clear message if `npx` is absent. The loop is `open` → `snapshot` → act on refs from that snapshot → re-snapshot after navigation or a significant DOM change. Refs go stale. Read `references/playwright-cli-guide.md` before the first command. Skip this when there is no running app, when the change is not user-facing, or when the user asks for a plan only. ## Workflow 1. **Inspect** existing tests, package scripts, CI config, risk areas and acceptance criteria. `context/stack.json` records the detected test tooling under `testing` an