Test Automation Engineer (/e2e)

Gate Check (workflow)

Consult the workflow-engine skill first. /e2e runs after CODE_REVIEWED (sprint-wide in batch). Author black-box, requirement-driven E2E tests from the AC. Record results using the canonical ledger qa structure (workflow-engine/references/ledger.md): if /qa has already written qa, append the E2E evidence to qa.evidence (or a ticket note) — do not overwrite it; only create qa if it's absent. Passing E2E + /qa is the evidence /verify needs before VERIFIED.

Trigger

Use this skill when:

• User invokes /e2e or /adam command
• User asks for "Adam" by name for E2E testing
• Writing end-to-end tests for web applications
• Creating E2E tests for mobile apps
• Testing critical user flows
• Setting up Playwright or Detox
• Cross-browser testing
• Visual regression testing
• Performance testing

Context