/e2e
E2EUser-invoked

Keep the E2E harness and CI test jobs healthy — fix flakes, shard work, cover critical journeys. Skill id `e2e`; agent id `tester`.

When to use

Flaky or slow E2E CI, new critical journey coverage, or trace-driven triage of failing test jobs.

Prerequisites

  • An E2E harness or CI test jobs (often Playwright) to stabilize or extend.

How to use

  1. Invoke /e2e with the failing journey, flake symptom, or new coverage goal.
  2. Share CI links or traces when available.
  3. Confirm wait strategy, quarantine owner, or shard plan the agent proposes.
  4. Re-run CI; escalate product bugs to /dev or deploy issues to /devops.

Done when

The targeted journey is green or quarantined with an owner, and CI sharding/waits are documented if changed.

Pipeline

Upstream
CI test failure or suite map
Downstream
/dev (product bug) · /devops (deploy) · /code-review

Boundaries

Not unit/seam TDD (/dev). Not deploy or build Knowledge fixes (/devops). Not the pre-merge three-axis review.

Sample prompt

prompt
/e2e

Playwright CI flakes on checkout journey

Agent

PRINCIPAL TESTER

Owns: Playwright suite, flake elimination, CI sharding, traces

Use the tester to [task]
tester
← Skill catalog