It asks the one fact it can't check before it builds on it.
Claude Code. With moo off, you ask: some customers were charged twice this week; find the cause and make sure it can't come back, with /freeze /widen /deepen /anchor named. Claude says those aren't installed skills, so it doesn't run them, and traces every double charge to a production override that retries timed-out charges, lists seven to refund, €580.96, adds an idempotency key with tests, and says it couldn't check whether the provider honors it. With moo on, you type /hope:compose and the same words. Each move takes over as it comes up: /freeze while it reads the production snapshot, then /deepen. A dialog asks the one fact it can't check: whether the payment provider honors an idempotency key; you answer yes, with a note that their docs say a repeat within 24 hours returns the first charge. It writes tests that fail on today's code, and /widen and /anchor follow. The reply says to set the timeout to 3000 ms with no retries, then gives the cause, the seven charges to refund, and a table of what is tested and what is proposed.