e2e-test-plan

# E2E Test Plan Skill

## Overview

This skill creates exhaustive, browser-testable E2E test plans by deeply analyzing Laravel Filament applications. It documents all pages, user roles, critical flows, navigation coverage, and detailed test scenarios that can be executed step-by-step by a QA tester who has never seen the codebase.

## Standard Plan Location

**Default output**: `docs/detailed-test-list.md`

This skill ALWAYS saves the test plan to `docs/detailed-test-list.md` unless a custom path is specified via the `--output` flag.

**Important**:
- Create the `docs/` directory if it doesn't exist
- Use the Write tool to save the plan to the standard location
- In update mode: Merge new discoveries with existing plan content
- Use `--force` flag to completely overwrite existing plan
- Use `--quick` flag for basic plan without deep discovery

## Purpose

Generate structured test plans that ensure:
- All pages are identified and will be tested
- All user roles are mapped with their permissions
- Critical user flows are documented
- Test scenarios cover positive and negative cases
- **100% NAVIGATION COVERAGE**: Every menu item and internal link is tested
- Cross-user interactions are documented
- Every test can be executed by someone who never saw the codebase
- Priority levels guide test execution order

## Review and Update Mode

When `docs/detailed-test-list.md` exists (and no `--force` flag), operate in **review and update mode**:

### Step 0a: Read Existing Plan

1. **Parse Existing Plan Content**
   - Read `docs/detailed-test-list.md`
   - Extract existing pages from navigation registry
   - Extract existing roles from test user accounts
   - Extract existing flows from test sections
   - Extract test credentials
   - Note the previous "Generated" date

### Step 0b: Validate Existing Content

1. **Validate Pages**
   For each page in the existing plan:
   - Check if the route still exists in the codebase
   - For Laravel: Check routes/web.php, Filament resourc