Install any skill in seconds. Free to start, no credit card required.
Get Started Free →danium/provocation
Edward de Bono's Provocation (Po) technique — state something deliberately wrong or absurd about the problem, then extract useful "movement" from it instead of judging it.
Passed 18 of 23 test cases with the skill, and 4 of 23 without it.
and 17 more in the full report
14 fixed4 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a critical PR pending in our GitHub repo (PR #402) that refactors our auth middleware. Here is the diff. Please analyze this code for bugs, race conditions, and performance bottlenecks, and give us a final pass/fail code review recommendation.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to perform the code review or debug the pull request. | Missed | Passed |
| Recommends an analytical review methodology or testing approach. | Passed | Passed |
The instructions your model reads when the skill loads.
State something deliberately wrong, impossible, or absurd about the problem — then refuse to judge it. Instead, ask what useful movement the statement creates: the principle hiding inside it, what would happen moment-to-moment if it were true, what that makes different from today. The absurd statement is not a proposal; it is a stepping stone you stand on only long enough to reach somewhere you could not have walked to directly. It works because judgment and movement are opposite mental motions, and every honest constraint you carry is also a wall you have stopped seeing.
Source: Edward de Bono, Po: Beyond Yes and No (1972) and Serious Creativity (1992).
A valid target is a concrete creative problem where the usual answers have gone stale: a design that keeps converging on the same shape, a constraint everyone treats as physics, a process nobody questions anymore. Good phrasings: "reinvent how we onboard new users", "our pricing page always ends up looking identical to competitors", "the approval step feels untouchable — challenge it". If the target is unclear, ask one focused question — "What's the problem, and which constraint or convention feels most fixed?"
Refuse requests to perform analytical work — debugging, reviewing code, implementing a change — and suggest an analytical approach instead. Redesigning or ideating about such a process is a valid creative target: "reinvent our code-review ritual" is in scope; "review this PR" is not.
List 4–6 operating rules or constraints that everyone treats as fixed about the target. Write them as flat declaratives, not questions — the things so obvious nobody says them out loud. These are the walls. Each one is a candidate to break, invert, or exaggerate in the next step. If you cannot name at least four, the target is probably too vague; go back to Step 1.
Draw across the five classical operations. Prefix each with Po: and keep it to one line. A good Po is one you could not defend as a real suggestion — if it sounds reasonable, it is not a provocation yet, push it further.
Po: the checkout has no prices.Po: the user reviews the software's work.Po: onboarding takes three seconds.Po: you pay the invoice before the work is scoped.Po: the page reads the visitor's mind.Cover at least three of the five operations across the batch. Do not run more than eight in one batch.
Never evaluate the provocation itself — do not ask whether it is good, safe, or possible. That is judgment, the wrong motion. Instead extract movement three ways:
test cases passed, vs 4 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.