What problem does it solve? Some requirements can never turn red in automated tests—scroll position persistence, block highlight order, what the user sees after pressing undo. This Skill guides you in writing manual acceptance checklists that a human can actually execute, while avoiding the three known failure modes of such checklists. ## Core Features & Use Cases - Testability triage: Before writing a manual item, determine whether the requirement is truly untestable or just not yet decomposed—split off the mechanizable half into automated guardrails. - Three-part acceptance items: Every item must state what it tests (motivation), how to operate it (a verified step-by-step sequence), and what both good and bad outcomes look like. - Baseline control groups: Distinguish failures caused by your code from host-environment behavior by requiring baseline measurements and "no worse than baseline" criteria. - Use Case: When shipping a Blockly-based editor change, produce a checklist table with screenshot-based verification of toolbox categories, dragged blocks, and cross-language block consistency. ## Quick Start Write a manual acceptance checklist for the undo behavior requirement, with steps, expected good and bad outcomes, and a host-environment baseline comparison.
