e2e-planlisted

# e2e-plan > **Mobile scope:** this command targets browser/web E2E only. For native iOS, native Android, or React Native E2E planning, switch to the `mobile-e2e-strategy` skill — Playwright is not the right tool for native UI flows. ## Instructions ### 1. Gather context - Ask the user: > 1. Which URL/page should be explored? (e.g., `http://localhost:3000/dashboard`) > 2. Which feature area? (e.g., "checkout flow", "user settings", or "all visible flows") > 3. Is there an existing seed/setup file? (e.g., `tests/e2e/fixtures/auth.ts`) - Read the Playwright guideline: `../../docs/guidelines/e2e/playwright.md` - Check for existing test plans in `specs/` or `tests/e2e/specs/`. ### 2. Explore the application - Use Playwright MCP tools to navigate the target URL. - Take a browser snapshot to understand the page structure. - Identify all interactive elements: forms, buttons, links, modals, navigation. - Map primary user journeys and critical paths. - Consider different user roles and their typical behaviors. ### 3. Design test scenarios For each discovered flow, create scenarios covering: - **Happy path** — normal user behavior, expected outcomes - **Edge cases** — boundary values, empty states, long inputs - **Error handling** — validation errors, server errors, network failures - **Negative tests** — unauthorized access, invalid data ### 4. Write the test plan Save as a Markdown file (ask user for location, default: `specs/plan.md`). Format: ```markdown # [Feature A