task-from-cypresslisted

# Task from Cypress ## When to use this skill The user typed `/tcgflow-task-from-cypress` or said: *"create tasks from failing tests"*, *"what's flaky?"*, *"process the Cypress run"*, *"fix the E2E suite"*. Triggered manually or by inspecting a recent CI run. ## Procedure 1. **Get failing/flaky specs.** Sources, in order of preference: - The Cypress MCP if configured (gives structured run data: failure count per spec, retries, screenshots). - The local `cypress/` folder + a recent `cypress run` output if the user just ran it. - A CI run output pasted by the user. 2. **Classify each failure** — propose one of these labels per spec (user adjusts): - **flaky** — passed previously, fails sometimes. Acceptance: "spec passes 10 consecutive runs locally" or "spec moved to quarantine list per `governance.md`." - **genuinely-broken** — application bug. Acceptance: "spec passes against current build; root-cause documented in subtask body." - **test-itself-wrong** — selectors are stale, fixtures wrong, assertions outdated. Acceptance: "spec rewritten against current UI; new selector strategy documented." - **pending** — test exists but is `.skip`'d or has open TODOs. Acceptance: "remove `.skip`, implement remaining steps, spec passes." 3. **Dedup against existing tasks.** Search `tasks/active/`, `tasks/completed/`, `tasks/archive/` for prior tasks referencing the same spec file. If found, append a new subtask to the existing task instead of creating a duplicat