qalisted

# qa — baseline-referenced QA (checklist → verification → defect report) Once a feature is on a server, **compares it against the plan of record**, finds what diverged, and hands it over in a shape engineering can act on directly. **The premise**: no verdict without a baseline. Not "this looks wrong" but **"this breaks rule X in document Y"**. An item with no baseline is not a defect — it is `needs confirmation`. ## When to invoke - A dev or staging deploy has been announced and the behaviour needs looking at - A reported defect needs reproducing and confirming - A pre-release sweep for anything the plan called for and the build is missing - **A checklist only**, with no verification (`baseline` mode) ## When NOT to invoke - Auditing the design's own structure and naming → `/fig:lint` - Carrying design-versus-code differences back into the file → `/fig:code` - Reviewing a document or a message → not this skill - Filing defects as tickets → whatever ticket tool you use. This skill stops at the report ## Inputs - `source` (required): where the request came from — a thread link, a page, or the request as spoken - `target` (required): the screen or feature under verification - `mode` (optional): `baseline` (stop at the checklist) / `full` (verify and report). Omitted, it asks - `env` (optional): the address, the account scope, the data scope to test against (branch, org, and so on). Given a name alone, the address is looked up in `qa.environments` ## Modes baseline