to-qc

Write QC_<date>.md — the plan the run-qc skill executes.

It is written for the agent that will run it, not for a person. Every item states one action and one result comparable enough that two readers cannot disagree about it.

Explore, then interview, then write.

Explore

Work out what changed between what runs in production and the candidate. Date production by probing it — a ticket that is Done is merged, not deployed.

Past the commits, what decides the plan: migrations, dependency and image changes, new environment variables, new outbound destinations, new scopes, new scheduled work, and anything that writes into a system you do not own.

Interview

Use the grilling skill. Look the facts up yourself; these are the user's to answer: