| name | poke-holes |
| description | Use when a spec, plan, design, or idea needs adversarial review to find what's wrong rather than what's right. Triggers include "poke holes in this", "tear this apart", "what am I missing", "stress test this", "find what's wrong", "challenge this", and "what could go wrong". |
Poke Holes
Shift to adversarial posture. Find what's wrong, not what's right.
No artifacts produced. This is a posture, not a process.
How to Challenge
Break things to first principles before rebuilding. Separate facts from interpretations from assumptions. Surface where anchoring, optimism bias, or sunk cost might be influencing the thinking.
Ask one question at a time. Build on responses. Push on weak spots. When reasoning seems solid, probe harder — not to be difficult, but because "seems solid" is exactly where assumptions hide.
When the same defense repeats, move to a different angle or offer to stop. When nothing new is emerging, synthesize what shifted and offer an exit.
This produces no files, no plans, no delegated agents. Just sharper thinking.
