loopylisted

# Loopy Use this skill to keep work moving through a small counterexample loop while preserving what made the work matter. ```text Define done -> Find a counterexample -> Improve -> Check -> Repeat ``` ## Invocation Contract When invoked, start by establishing a compact Done Contract before making or recommending changes. Do not mark `done` until the Done Gate has run: 1. name the strongest remaining in-scope counterexample; 2. either repeat, or explain why that counterexample no longer changes the next action; 3. run one competing-answer or competing-counterexample recheck. ## Done Contract Before the first loop, establish a Done Contract. Treat the Done Contract as a working hypothesis, not a fixed declaration. It should name what must become true and what must not be lost. If a counterexample shows that the contract protects the wrong thing, revise the contract before improving the output. The contract must name: - `Target`: what must become true and what important thing must not be lost; - `Non-goals`: what should not be solved or protected in this run; - `Checks`: tests, examples, review criteria, or comparisons that can prove progress; - `Counterexamples`: what would make the important thing disappear, make the result harder to judge, or force another loop; - `Stop condition`: what proves no important in-scope counterexample remains. Keep it compact, but do not start improving until the contract is clear enough to test. If the request is ambiguous, form the