workflow-e2e-authorlisted
Install: claude install-skill MartinKChen/harness-claude-code
# workflow-e2e-author
Translate the named `e2e` tasks on a slice into Playwright specs. Dispatched with a (slice #, task ids) pair — the agent reads the slice body's `## Tasks` checklist for the named ids, the slice branch, the worktree path, and the slice's Acceptance criteria.
The agent loads its own pattern set (E2E conventions, semantic selectors, fixture isolation, etc.) at kickoff. This skill owns only the workflow: read → worktree → write → tick → commit → push → comment.
## When to activate
Activate this skill whenever:
- The dispatch prompt opens with `Author E2E for slice #<n> tasks <ids>`.
- The user types `/workflow-e2e-author`, or phrases like "author the E2E specs for slice #<n> tasks e2e.1,e2e.2".
Do NOT activate to address coverage-gate findings on a slice (use `workflow-e2e-fix`), or to write production code (engineer's lane).
## Input contract
Read the slice issue #<n> body. Locate the task block(s) for <ids> in the `## Tasks` checklist (each entry is a header `[ ] \`<id>\` · **<type>** · blocked-by <ids|—>`, the delivery on the next line, a metadata line tagging `covers:` (AC clause ids) + the realized critical-path Journey step / `entry-source:` / `done:`, then `scenario:` and a fenced ```gherkin block of named Scenarios to walk). The checklist is the durable task ledger — a box already checked `[x]` means that task is DONE; skip it (resume safety). Read the slice's Acceptance criteria (EARS) plus the e2e task's own `scenario:` Gherkin for behavior