Agent skill

Provocation

by danium in danium/lateral-thinking

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.

MITAuto-check passedDevelopment

Install Provocation

skills CLI
$ npx skills add danium/lateral-thinking --skill provocation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install danium/lateral-thinking provocation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/danium/lateral-thinking.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/provocation .claude/skills/provocation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
provocation
GitHub stars
318
Token cost
~1.7k tokens
SKILL.md length
1,018 words
Files
3 (incl. references)
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 6 steps: Confirm the target → Surface the rules → Generate 4–6 provocations → …
  • A constraint feels unbreakable
  • SKILL.md covers What this technique does, Workflow, Honesty mechanics and What NOT to do, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Provocation is an agent skill from danium/lateral-thinking. 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. Use when a constraint feels unbreakable, when every design converges on the same shape, or to escape "the way it's always done". Triggers include "provocation", "po", "absurd statement", "deliberately break the rule", "the constraint feels unbreakable", "sacred cow". Do NOT use for analytical work like debugging, code review, or implementation…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/provocation-templates.md` and `references/worked-example.md`).

It sits in Development. The repository describes itself as: Lateral thinking skills for AI agents - 8 techniques + a router. de Bono for your coding agent. The licence is MIT.

When your agent uses it

  • A constraint feels unbreakable
  • Every design converges on the same shape
  • Escape the way its always done
  • Include provocation

Example prompts

  • “movement”
  • “the way it”
  • “. Triggers include”
  • “/provocation”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Confirm the target
  2. Surface the rules
  3. Generate 4–6 provocations
  4. Movement, per provocation
  5. Meta-pattern scan
  6. Honest ranking

What it can do on your machine

Read from SKILL.md and the folder at commit bde713d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Provocation loads about 1.7k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 134 tokens; SKILL.md has 1,018 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~134
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danium/lateral-thinking at commit bde713d, republished under its MIT licence (© danium). 1,018 words, ~1,749 tokens.

Download SKILL.mdSave it as .claude/skills/provocation/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
provocation
description
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. Use when a constraint feels unbreakable, when every design converges on the same shape, or to escape "the way it's always done". Triggers include "provocation", "po", "absurd statement", "deliberately break the rule", "the constraint feels unbreakable", "sacred cow". Do NOT use for analytical work like debugging, code review, or implementation tasks.

Provocation (Po)

What this technique does

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).

Workflow

Step 1: Confirm the target

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.

Step 2: Surface the rules

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.

Step 3: Generate 4–6 provocations

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.

  • Escape — drop a rule entirely. Take a rule from Step 2 and state its absence as fact. Po: the checkout has no prices.
  • Reversal — invert a relationship. Flip who does what to whom, or which direction something flows. Po: the user reviews the software's work.
  • Exaggeration — push a quantity to an impossible extreme (up or down to zero). Po: onboarding takes three seconds.
  • Distortion — scramble the normal sequence or swap the roles in it. Po: you pay the invoice before the work is scoped.
  • Wishful thinking — state a fantasy as accomplished fact. 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.

Step 4: Movement, per provocation

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:

  • (a) The principle — what general idea is hiding inside the absurd statement?
  • (b) Moment-to-moment — if it were literally true, what would happen, step by step, in the first minute?
  • (c) The difference — what is concretely different from how things work today?

Then shape any live thread into a real idea. Not every provocation reaches one — that is expected and honest (see Honesty mechanics). Show the movement work, not just the idea it produced.

Show full SKILL.md (435 more words)Show less
Step 5: Meta-pattern scan

Scan across the ideas that landed for a structural property that kept recurring — "every provocation that paid off removed a step rather than adding one", "the strong ones all shifted work from the user onto the system", "three of them turned a cost into a signal". State the structural insight explicitly. This cross-provocation observation is often where the deepest result lives, and it also explains why the abandoned ones failed.

Step 6: Honest ranking

Pick the 2–4 sharpest directions and rank them. Say which feel weak, and why. Then offer next moves and stop: run more provocations, go deeper on one direction, switch to a different technique, or stop here. Never push the user to commit — divergence is your job; the decision is theirs.

Honesty mechanics

A provocation that yields no movement after two honest attempts is abandoned visibly. Show it, for example:

Po: customers pay us to leave — no movement found. Moving on.

Roughly 1 in 3 provocations will not pay off. A batch where every single Po produces a clean idea is a tell that the movement was faked — the operator judged the provocations into safe suggestions instead of moving off them. Show the failures; they are what proves the rest are real.

When the batch itself fails. If almost nothing moves, the problem is upstream of the provocations. Do not write more of them. Name the diagnosis, suggest the technique that fits it as the user's next move, and stop there — do not run it yourself:

  • Step 2 could not produce four rules everyone treats as fixed → the target is too vague, or it is not actually fenced. Suggest random-stimulus, which needs no constraint to push against.
  • The rules are real but every Po lands back on the same idea → you may be solving the wrong problem. Suggest concept-fan, which climbs to the concept the target serves.

What NOT to do

  • Don't defend or attack the provocation. It is not a proposal. Arguing "that would never work" or "actually that's reasonable" both miss the point — extract movement instead.
  • Don't generate polite, plausible provocations. If a Po could pass as a genuine suggestion, it is not a provocation. Push it until it is clearly absurd.
  • Don't skip the movement structure. Jumping straight from the Po to a finished idea hides the reasoning and usually smuggles in an idea you already had.
  • Don't run more than 8 provocations per batch. Quality drops and the movement work gets rushed.

References

© danium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/provocation of danium/lateral-thinking.

  • SKILL.md
  • references/provocation-templates.md
  • references/worked-example.md

Open the folder on GitHubat commit bde713d

Compare with similar skills

Provocation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Provocation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Provocation this skilldanium/lateral-thinking318—~1.7kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from danium/lateral-thinking

All 10 skills in this repo
  • Analogy

    danium/lateral-thinking

    Forced Analogy / Structural Transplant — map the problem onto a structurally similar system from a distant domain (immune system, air-traffic control, restaurant kitchen, jazz ensemble) and transfer…

    318 GitHub stars~1.6k tokensUpdated 24 days ago
    Auto-check passed
  • Concept Fan

    danium/lateral-thinking

    Edward de Bono's Concept Fan — climb from the current solution to the concept it serves by asking "what is this a way of doing?", then fan out alternative concepts and concrete implementations for…

    318 GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Inversion

    danium/lateral-thinking

    Assumption Inversion — list the assumptions behind the current approach and flip each one, then ask where the flipped version could actually be true.

    318 GitHub stars~1.5k tokensUpdated 24 days ago
    Auto-check passed
  • Random Stimulus

    danium/lateral-thinking

    Edward de Bono's Random Stimulus technique — force-fit a random unrelated object, place, or phenomenon onto a creative target to break familiar association patterns.

    318 GitHub stars~2.3k tokensUpdated 24 days ago
    Auto-check passed
  • Scamper

    danium/lateral-thinking

    SCAMPER (Bob Eberle) — run one existing idea, product, or process through seven systematic transformations - Substitute, Combine, Adapt, Modify/Magnify, Put to other use, Eliminate, Reverse/Rearrange.

    318 GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed
  • Six Hats

    danium/lateral-thinking

    Parallel thinking with six enforced perspectives, based on Edward de Bono's Six Thinking Hats® method - examine one decision through sequential passes for facts, feelings, risks, benefits…

    318 GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed

Categories

Questions about Provocation

What does Provocation do?

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. Provocation is an agent skill from danium/lateral-thinking. 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.

When should I use Provocation?

Provocation fits situations like: A constraint feels unbreakable; every design converges on the same shape; escape the way its always done; include provocation.

How do I install Provocation in Claude Code?

Run `npx skills add danium/lateral-thinking --skill provocation -a claude-code`. Or copy the skill folder (skills/provocation in danium/lateral-thinking) into .claude/skills/provocation in your project. Claude Code loads it when a task matches its description.

How do I install Provocation in Codex?

Run `npx skills add danium/lateral-thinking --skill provocation -a codex`. Or copy the skill folder (skills/provocation in danium/lateral-thinking) into .agents/skills/provocation in your project. Codex loads it when a task matches its description.

Can I use Provocation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danium/lateral-thinking --skill provocation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provocation, .gemini/skills/provocation, .github/skills/provocation and .opencode/skills/provocation in your project.

What does Provocation need to run?

SKILL.md names no scripts, command-line tools or credentials: Provocation is instructions for the agent only.

Does Provocation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Provocation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Provocation use?

Provocation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Provocation use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Provocation?

Skills that share tags, products or a category with Provocation: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Provocation?

danium (a GitHub user) maintains it in danium/lateral-thinking, which has 318 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 13, 2026.

Source: danium/lateral-thinking on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.