qa-escape

An escape is a bug a human found after an agent's checks said the work was done. qa-escape turns each one into three things: a reproduction, a regression test to write first, and a recorded escape class that every future ticket in that area is checked against. The goal is that a class escapes at most once before the checks change.

Inputs

• QA report — steps, expected, actual, environment, screenshots or logs. Missing expected or actual → ask for that one field.
• The issue and its PR — the ticket QA tested and the PR that shipped it. Read the PR's agentic-qa and risk-review marker comments and the /tdd-loop summary if present: they are the agent's claim.
• Isolated worktree — only when reproduction is needed, use <project-repo>/.worktrees/qa-escape-<issue> detached at the revision QA tested: use git worktree add --detach per workspace policy. Only an explicitly started /factory run or /orchestrate-t3 may read/follow using-git-worktrees for its task setup; direct skill use requires the user's invocation. Before the first command there, verify and report the checkout record the workspace AGENTS.md requires: path, owning repository and common Git directory, branch or detached state, starting commit, and baseline. Setup failure or a mismatch blocks the run; never fall back to the main checkout. Leave the worktree in place and report its path; cleanup follows the workspace rules.
• Environment — local, staging or production. Production evidence is pasted only. Staging needs this session's explicit user approval and user-provided SSH access; each mutation requires separate approval.

Rules