track-qa
Track QA
Manual QA tracking activated — I'll use QA.md to capture and manage the hands-on verification checklist that tests can't cover.
Overview
Use QA.md in the project root to maintain the manual QA checklist — the items a human has to exercise (visual rendering, multi-step flows, race conditions, integrations) before declaring a release ready. Tools that consume the cc-dash/qa@1 schema can ingest the file: surface pending items in a portfolio queue, drive approve/fail/skip workflows with notes, and run focused review sessions across many items at once.
Core principle: Tests prove correctness; QA proves shippability. Maintain a living, executable checklist of everything tests can't catch, so "ready to ship" is a verifiable state, not a vibe.
Usage Modes
This skill supports five modes via optional arguments:
| Mode | Command | What it does | Use when |
|---|---|---|---|
| Generate | /track-qa or /track-qa generate |
Interactive QA discovery and QA.md creation | First time setting up manual QA for a project |
| Update | /track-qa update |
Add, remove, or edit QA items in an existing QA.md | New features shipped, QA scope changed |
| Audit | /track-qa audit |
Re-evaluate items against current state; identify stale or obsolete checks | Periodic review, before a release window |