e2e-evidence

What problem does it solve?

This Skill prevents weak or misleading end-to-end closure by telling you exactly which Playwright tier to run and what test output counts as real evidence before archiving.

Core Features & Use Cases

• Playwright tier selection: Decide between Tier 1 (boot, crud, website-export, duplicates) and Tier 2 (adds panels, reactivity, imports) based on what user-facing goal your plan touches.
• Evidence-based close-out guidance: Ensure your close-out notes include the actual tail lines from test runs (e.g., “N passed”) rather than summaries or claims.
• Failure ownership discipline: When [boot] / [crud] / [panels] / [reactivity] / [imports] fail or are flaky, route the fix to the owning plan or require a separate plan explicitly covering the fix before archive.
• Project-to-user-goal mapping: Know which Playwright project name protects which user-observable surface so you can route new specs correctly.

Quick Start

Decide which tier fits your change and paste the required “npm run test:e2e” and, if needed, “npm run test:e2e:full” tail output lines into your plan close-out evidence.