メニュー
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | socratic |
| description | Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing. |
| user-invocable | true |
Guide discovery through systematic questioning, helping examine a belief, decision, or idea more deeply.
Work through multiple levels of questioning to explore the topic. The goal isn't to prove the person wrong—it's to help them (or yourself) think more clearly and deeply.
Topic/Belief: [What we're examining]
The Claim/Position [Restate the belief or idea being examined]
Questions
Reflections [What these questions reveal about the claim]
Hidden Assumptions
| Assumption | Question to Test It |
|---|---|
| [assumption 1] | "Is it always true that...?" |
| [assumption 2] | "What would need to be true for...?" |
Questions
Questions
Questions
Questions
Steel Man The best argument against this position:
[Strongest counterargument]
Refined Position After questioning, a more nuanced view might be:
[Refined statement]
Remaining Questions
Key Insight The most valuable thing this questioning revealed:
[Insight]
$ARGUMENTS
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
Cynefin sense-making framework categorizing problems as Simple, Complicated, Complex, Chaotic, or Confused to select the right approach. Use when unsure how to tackle a problem.
