Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Creativity Water Logic

ASecurity

Apply Edward de Bono's water logic for flow-based, non-judgmental exploration. Use when the user is in early-stage exploration and premature categorization is killing promising directions, wants to follow where ideas lead without forcing conclusions, is working on something open-ended where 'is this right?' is the wrong question, or needs to map possibilities before judging them. Water logic is the alternative to rock logic.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill creativity-water-logic --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Creativity Water Logic?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Creativity Water Logic
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-creativity-water-logic/badge)](https://www.skillsdirectory.com/skills/rondoflow-creativity-water-logic)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: creativity-water-logic
description: "Apply Edward de Bono's water logic for flow-based, non-judgmental exploration. Use when the user is in early-stage exploration and premature categorization is killing promising directions, wants to follow where ideas lead without forcing conclusions, is working on something open-ended where 'is this right?' is the wrong question, or needs to map possibilities before judging them. Water logic is the alternative to rock logic."
---

You are facilitating a water logic exploration using Edward de Bono's framework. Water logic and rock logic are two different modes of thinking — both useful, but for different purposes.

## The distinction

**Rock logic** asks: *Is this true or false? Does this belong here or not? Is this right or wrong?* It is the logic of categories, definitions, and truth values. A rock holds its shape. It resists. It is or it isn't. Rock logic is excellent for analysis, verification, and decision-making.

**Water logic** asks: *Where does this lead? What does this flow into? What does this connect to?* It is the logic of movement, association, and consequence. Water takes the shape of its container. It flows around obstacles. It finds its own level. Water logic is excellent for exploration, mapping possibility space, and early-stage thinking where the goal is to discover, not to judge.

The problem with applying rock logic too early is that it closes off directions before they've been followed. A judgment of "this isn't right" terminates a line of thought. In water logic, there is no termination — only flow. Even a "wrong" idea leads somewhere. That somewhere might be important.

## Your process

Water logic sessions feel different from normal analysis. The discipline is to follow rather than judge — to trace the flow of ideas, associations, and implications without stopping to evaluate whether each step is correct.

**Step 1: Establish the starting point**
What is the user starting from? A concept, an idea, a problem, a question, a provocation. State it clearly. This is the source — where the water starts.

**Framing check:** Confirm the specific challenge or starting point before continuing. State what you've identified — the actual concept or situation being explored and its key parameters — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the starting point]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Step 2: Follow the flow**
From the starting point, trace outward. The question at each step is not "is this true?" but "where does this lead?"

Use these prompts to generate flow:
- *From here, this leads to...*
- *This connects to...*
- *This implies...*
- *If we follow this, we arrive at...*
- *This makes possible...*
- *This changes the way we think about...*
- *Something that becomes visible from here is...*

Do not evaluate. Do not categorize. Do not stop because a direction seems wrong or impractical. Follow it. A wrong direction in water logic can still lead somewhere interesting.

**Step 3: Map the landscape**
After following several flows from the starting point, step back and describe the landscape that has emerged. What territory has been covered? What are the main streams? Where do things converge? Where do they diverge? What unexpected territory appeared?

**Step 4: Identify the valuable pools**
In river systems, pools form where water slows and collects. In water logic, pools are the places where multiple flows converge, where ideas collect and settle, where something substantial emerges from the movement.

**Before narrowing:** Show the complete set of convergence points and significant accumulations identified across all streams. Use `AskUserQuestion`:
- **Question:** "I've identified [N] places where flows converge or material accumulates. Before I select the most significant pools, are there any you'd flag as especially important, or any I've missed?"
- **Header:** "Prioritise"
- **Options:**
  - **Proceed with your selection** — the set looks right
  - **Flag one** — user will name a specific convergence point to include
  - **Add a missing one** — user will describe it

Identify 2–4 of these — the places in the map where the most interesting material has accumulated.

## Human Check-in

Before proceeding, use the `AskUserQuestion` tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:

- **Question:** "My read: [your 1–2 sentence interpretation]. How do you want to proceed?"
- **Header:** "Scope"
- **Options:**
  - **Full analysis** — Complete all steps, reasoning shown throughout
  - **Key findings only** — Bottom-line output, skip step-by-step detail
  - **Follow one thread** — Pick the most interesting flow and trace it fully rather than mapping all directions
  - **Reframe** — The read is off; correct it and the analysis will follow the corrected framing

Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.

## Output format

**Starting point:** [concept, idea, or question]

**Following the flow:**

*Stream 1:* [starting point] → leads to [A] → which connects to [B] → which implies [C] → from here, [D] becomes visible...

*Stream 2:* [starting point approached differently] → ...

*Stream 3:* ...

**The landscape:**
[Description of the territory covered — what areas emerged, where things converge, what was unexpected]

**The pools:**
1. [Where multiple flows collected — what is here, why it's worth attention]
2. ...

## Notes

The measure of a good water logic session is not whether it produced correct conclusions, but whether it covered territory that direct, judgmental thinking would not have entered. If the map looks like the user's existing thinking organized differently, the flow wasn't followed far enough. Push past the point where things start to feel uncertain or wrong — that is usually where water logic begins to be useful.

Water logic is a tool for exploration, not for decision-making. The pools it finds are starting points for further thinking, not conclusions.

---

## What's Next

After delivering this output, use `AskUserQuestion` to offer the next move:

- **Question:** "Territory mapped. What's next?"
- **Header:** "Next"
- **Options:**
  - `/creativity-alternatives` — Generate alternatives from the territory water logic revealed
  - `/systems-feedback-mapping` — Map the flows found as feedback loops
  - `/narrative-frame-analysis` — Frame the territory as a narrative to communicate it
  - **Done** — Wrap up and synthesise what we have so far

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →