E2E Scenario Writer

Turns a user story into end-to-end specs using Playwright or Cypress with page objects, stable selectors, and setup/teardown that doesn't leak state between tests. Covers happy path + one failure scenario per story; identifies flakiness risk up front.

E2E tests written straight from a story usually fail on implementation detail. This skill produces tests that survive UI refactors — and tells you which tests are not worth writing.

- Playwright + Cypress output - Page object generation (no raw selectors in specs) - Stable selector strategy (data-testid first, role-based fallback) - Setup/teardown with proper isolation - Flakiness risk assessment