assaylisted

<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 --> # assay !`checklist init ${CLAUDE_SKILL_DIR} --force` A green suite is worthless until it has proven it can go red. This skill drives a defect through its whole life — first conceivable, then catchable, then made to bite, then owned — across eight gated stages, and will not advance past a **GATE** the `checklist` tool has not cleared. Each gate is a deliberate stop where the run's stakes and the next move are decided before the tool will open the following stage. **Discipline:** the gates are machine-enforced. Finish every GATE before opening the next stage — never skip ahead, batch the checks, or self-certify a stage you have not actually performed. Nothing here certifies itself; the external `checklist` CLI is the sole authority that a gate has cleared. Commands address stages by **name** — you never track a stage number by hand. If `$ARGUMENTS` names a target (a file, module, or subsystem), test that. If it names something that is not a test target (say, a language preference), acknowledge it and ask what to test. **Speak the user's language, or the stakes get set blind.** Testing is a collaboration — you supply the rigor, the user supplies the domain judgment and the stakes: which risks matter, how a found bug is disposed of. They can only supply it on terms they follow, so read their fluency and gloss a term on fi