What problem does it solve? Requests phrased as actions like "add retry" or "make search better" cannot be verified, so teams ship work against an unverifiable definition of done. This Skill turns any request into a set of falsifiable acceptance checks that are red today and can only go green when the real work is delivered. ## Core Features & Use Cases - Outcome reframing: Rewrites action-based asks as observable outcomes, then decomposes them into new-behavior, invariant, and edge-case claims. - Evidence typing and RED/GREEN validation: Assigns each claim a deterministic, empirical, or subjective evidence type, and confirms behavior checks fail on today's code for the right reason. - Adversarial hardening: Names the cheapest fake that could satisfy each check and closes it, producing a check list ready to anchor a test plan or feed loop-generator's author-loop as a .loop.yaml. - Use Case: Given "make the CSV export not choke on big files," produce a check list covering a 1,000,000-row export test, a memory ceiling measurement, a golden-file format guard, and RFC-4180 quoting edge cases, each labeled driver or guard with anti-gaming notes. ## Quick Start Ask the assistant to turn your feature request or task into a definition of done with falsifiable acceptance checks using the frame-checks skill.
