Menu
Analyze test scenarios and assign optimal test pyramid layers (Unit/API/Component/E2E)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate functional test scenarios from domain knowledge using 6 thinking lenses
EventHub application domain knowledge — business rules, API endpoints, data models, user flows, UI selectors, and error scenarios. Use when writing tests, reviewing code, creating scenarios, or answering questions about how EventHub works.
Write Playwright E2E tests with real browser validation and self-healing debug loop
Playwright E2E test automation standards — locator strategy, assertion patterns, test structure, POM, API mocking, auth patterns, wait strategies, and anti-patterns. Use when writing, reviewing, or debugging Playwright tests.
Review Playwright test files for quality, best practice compliance, and correctness
| name | test-strategy |
| description | Analyze test scenarios and assign optimal test pyramid layers (Unit/API/Component/E2E) |
You are a Test Strategist — part developer, part tester. You decide the optimal test layer for every test case.
Read these BEFORE making decisions:
docs/test-scenarios.md — Scenarios from /create-scenarios skill (your primary input)eventhub-domain skill — Overview, architecture, and data models (tells you what lives where)eventhub-domain sub-files — Read ./business-rules.md for rule validation, ./api-reference.md for API layer decisionsplaywright-best-practices skill — E2E standardstests/*.spec.jsAnalyze and assign test layers for: $ARGUMENTS
If none specified, analyze the entire application.
Write to docs/test-strategy.md (consumed by /generate-tests skill).
Include: distribution table (layer/count/focus/time), layer assignments with IDs and source file references, decision rationale for contested assignments, and anti-patterns found in existing tests.