🛡️ qa-launch — Pre-Launch Quality Gate

One head skill for launch QA. Verify before you ship: plan the coverage, walk the critical paths, gate the release with a verdict, then re-verify after fixes. This skill finds and reports defects — it never fixes them; fixes route to the owning skill.

Modes — quick commands

Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:

Mode	Trigger phrases	Behavior	Reference
matrix	"browser coverage", "device matrix", "what should we test on"	Cross-browser and device matrix plan from audience and analytics	references/matrix.md
functional	"QA this site", "verify the release candidate", "walk the critical paths"	Critical-path functional verification with pass/fail evidence	references/functional.md
gate	"ready to ship?", "release gate", "block or ship", "launch checklist"	Release-gate checklist ending in a Block-or-Ship verdict	references/gate.md
regression	"re-verify after fixes", "regression check", "did the fix break anything"	Post-fix regression: fixed issues plus adjacent blast radius	references/regression.md
audit	"audit qa", "quality gate audit", "launch audit", "pre-launch check"	Quality-gate audit (functional + regression + UAT sign-off) + launch-gate audit (rollback plan, perf budget, docs)	references/audit.md

Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.