e2e-architectlisted

# E2E Architect Skill Design and strategy for E2E tests. Complements `e2e-run`, `e2e-analyze`, and `e2e-fix-cycle` which focus on execution and fixing. ## Project Memory This skill reads and writes memory in the **project's** auto-memory directory to track architecture decisions across sessions. ### On Start — Read Memory Before executing, read `<project-memory-dir>/e2e-architect.md` if it exists. Use it to: - Know which areas have test plans already created - Recall audit findings from previous sessions - Reference fixture suggestions already made ### On Completion — Write Memory After execution, update `<project-memory-dir>/e2e-architect.md`: ```markdown # E2E Architect Memory ## Test Plans Created | Date | Feature | Spec File | Status | |------|---------|-----------|--------| | <date> | <feature> | <file> | planned/implemented | ## Audit Findings - **Last audit:** <date> — scope: <scope> - **Coverage gaps:** <list of uncovered routes/features> - **Anti-patterns found:** <count> ## Fixture Suggestions - <fixture name> — <purpose> — <status: suggested/implemented> ## Debug History | Date | Spec | Root Cause | Resolution | |------|------|------------|------------| | <date> | <file> | <cause> | <fix> | ``` The memory directory is the project's auto-memory path (e.g., `~/.claude/projects/<project-path>/memory/`). Create the file if it doesn't exist; merge with existing content if it does. --- ## Usage ```bash /e2e-architect <subcommand> [args] ``` | Subcommand