e2e-test-planlisted

# E2E Test Plan Generator This skill produces E2E test plans as **realistic user journey stories**, not the traditional matrix-style test case grids that try to cover every combination and usually fail. The output is a markdown file with checkboxes that a tester (human or agent) can run top-to-bottom without setting up artificial state — each step follows naturally from the previous one within a single user session. ## What is a "story" in this skill A story is **one complete user session driven by a real mission** — from app open to app close. The mission is the engine; the steps describe how the user pursued it. Narrative, not feature list. A single well-chosen mission naturally exercises most of an app's features along the way. Stories are NOT: a single user intent or feature, a short flow ("just login"), a matrix row, a coverage map walked end-to-end. Stories ARE: a coherent professional or personal mission, typically dozens of steps covering many features as a consequence of the mission, modeled on what users actually do (detours and corrections included), independent or sequenced. **Default to one story.** Add more only when one journey can't reasonably cover the scope — fundamentally different user roles (admin vs end-user), uninstall/reinstall flows, or a single story would balloon past one tester sitting. **Multiple stories should chain to minimize staging.** If Story 1 ends with a populated project, Story 2 starts from it rather than rebuilding. Each story st