What problem does it solve? End-to-end browser tests often become flaky, slow, and hard to maintain because they rely on brittle selectors, arbitrary sleeps, and non-deterministic data. This Skill provides a disciplined procedure for writing stable Playwright E2E tests that verify real user-visible behavior, including issue workflow states and human-in-the-loop blocker paths. ## Core Features & Use Cases - Stable Test Authoring: Enforces page objects, role/label/testid selectors, and explicit UI/event conditions instead of arbitrary waits. - Deterministic Setup: Guides creation of seeded fixtures so issue and workflow states are reproducible across runs. - Human-Loop Verification: Tests answer paths and blocked/unblocked states when human input gates a workflow. - Use Case: When a new issue workflow cockpit ships, use this Skill to write an E2E test that seeds an issue, walks the critical user path, and asserts the user-visible blocked and unblocked states with retained failure screenshots and traces. ## Quick Start Write a Playwright E2E test for the issue assignment flow using page objects, seeded fixtures, and assertions on the visible blocked and unblocked states.