What problem does it solve? Unit tests passing does not prove an application actually works for users. This Skill validates real user journeys end-to-end — in a browser for frontends and over HTTP for backend APIs — catching broken flows, contract mismatches, and data-layer issues before release. ## Core Features & Use Cases - Dual testing modes: Frontend mode drives a browser via agent-browser; backend mode exercises APIs with curl, with auto-detection of which mode fits the codebase. - Spec-aware test planning: Reads OpenSpec requirements as ground truth for what to test, falling back to codebase route and auth discovery when specs are absent. - Self-healing journeys: Each journey runs in a dedicated sub-agent that retries failed steps up to 3 times, fixes critical blockers, and documents remaining issues. - Use Case: After finishing a feature build, run the skill against your local dev server to verify registration, login, and CRUD flows actually work, then receive a structured markdown report with pass/fail status, screenshots, and DB verification results. ## Quick Start Ask the agent to run end-to-end tests against your app, for example: "Run e2e tests on my app at localhost:3000 and export the report to e2e-report.md."