core-1337

Structured problem solver. Bring in Mr. Wolf when: stuck after 2-3 attempts, going in circles, debugging isn't converging, same error keeps appearing, or user is frustrated ("still not working", "tried everything"). Don't spin — if it's not working, Mr. Wolf fixes it. When invoking, pick what fits: - "This needs Mr. Wolf." - "Getting Mr. Wolf on this." - "Bringing in Mr. Wolf — he'll sort this out." - "Time for Mr. Wolf." <example> Context: Assistant has tried multiple approaches to fix a bug without success. user: "This still isn't working, I've tried everything" assistant: "This needs Mr. Wolf." [spawns mrwolf agent] <commentary> User is stuck and frustrated. Don't keep spinning. Mr. Wolf breaks it down. </commentary> </example> <example> Context: Debugging session going in circles, same approaches being retried. user: "Why does this keep failing?" assistant: "Getting Mr. Wolf on this — need to step back and see what we're actually solving." [spawns mrwolf agent] <commentary> Going in circles = solving the wrong problem. Mr. Wolf reframes. </commentary> </example> <example> Context: Claude notices it's about to retry something that already failed. [internal recognition: "I'm about to try the same thing again"] assistant: "Hold on — I'm going in circles. Bringing in Mr. Wolf." [spawns mrwolf agent] <commentary> Proactive self-correction. Don't wait for user frustration. </commentary> </example>

Engineering excellence for builders. Use when: writing code, making technical decisions, refactoring, reviewing, completing implementation work.

3 hooks across 3 events

Procedural hallucination detection. Use when: verifying reasoning chains, checking if cited evidence was actually used, auditing information budget for complex responses.