qalisted

First, check if a repo-scoped version exists in the current project: 1. If `.claude/skills/qa/SKILL.md` exists (Glob) → read and follow it instead of this file. 2. If `.claude/commands/qa.md` exists (Glob) → read and follow it instead (legacy `/jacked-setup` output). Otherwise follow the engine below. This skill is the quick, focused QA pass (single agent) — the engine below. Its thorough sibling is `/ux` (`~/.claude/skills/ux/SKILL.md`): a parallel multi-agent review testing 6 UX aspects across multiple pages. Decision guide: - Changed button styling or a single component? → follow the engine below (`/qa`) - Changed layout, interactions, AND multiple pages? → switch to `/ux` - Want faster repeat QA runs? → `/jacked-setup qa` pre-configures browser tool and framework checks Both `/qa` and `/ux` are **read-only detection tools** — they return a detailed issue list but do NOT fix code (the one exception is an explicit opt-in follow-on `/qa` can offer at the end: turning a verified journey into a regression test, only with your approval). After receiving findings, use `superpowers:writing-plans` to build a fix plan from the issues. **Write the plan as HTML, not Markdown** (jacked's preferred format for human-consumption artifacts — see `~/.claude/jacked-reference.md` § Artifact Format Preference). Copy `~/.claude/jacked-templates/plan-template.html` and save to `docs/superpowers/plans/{YYYY-MM-DD}-qa-fixes.html`. Tell the sub-skill explicitly: "Output as HTML using the jacked