add-qa-migrationlisted

# QA Migration <!-- uses: - skill: add-subagent-driven-development - command: /add.build - command: /add.new - command: /add.plan - command: /add.qa-setup - command: /add.review --> Domain layer that turns an existing QA/test setup into the code-addiction QA pipeline by **dogfooding the framework's own feature chain** autonomously. **Core principle:** The migration is a real feature. Capture it via `add.new`, then run it through `add.plan → add.build → add.review` — no bespoke migration mechanism. > **Mechanism reuse:** This skill defines WHAT to dispatch and WHERE to pause. The HOW (dispatch template, decision log, review gates, compliance gate) comes entirely from `{{skill:add-subagent-driven-development/SKILL.md}}`. Do NOT re-invent dispatch machinery here. --- ## When to Use - `/add.qa-setup` detected an existing QA/test flow (Cypress, Jest, Vitest, Playwright-standalone, or a custom runner) on a project's **first** setup run and the user **confirmed** they want to migrate/adapt it. - The goal is to adopt code-addiction's dual-judge QA model over an existing suite, preserving intent, not to author QA from a blank slate. ## When NOT to Use - **No existing QA tooling** — nothing to migrate; run the normal `/add.qa-setup` scaffolding path. - **User declined migration** — never migrate silently; confirmation is mandatory upstream. - **Re-run of `add.qa-setup`** (config.json already present) — migration detection is first-run only; skip. - **A single trivial test file