feynman
Feynman Technique
Apply the full Feynman learning technique to deeply understand a concept.
Instructions
Work through all four steps of the Feynman technique. Be honest about gaps—they're the point.
Output Format
Concept: [What are we trying to understand?]
Step 1: Explain It Simply
Explain as if teaching someone with no background in this field
Simple Explanation
[Write a plain-language explanation. Use everyday words. Avoid jargon. Aim for a bright 12-year-old to understand.]
Analogy
[Create an analogy using something familiar to illustrate the concept]
Step 2: Identify Gaps
Where did the explanation get fuzzy, hand-wavy, or require jargon?
Gaps Found
| Gap | What I Said | What I'm Not Sure About |
|---|---|---|
| 1 | [vague part] | [the underlying question] |
| 2 | [vague part] | [the underlying question] |
| 3 | [vague part] | [the underlying question] |
Jargon Used
| Term | Can I Explain It Simply? |
|---|---|
| [term] | Yes / No / Partially |
Step 3: Fill the Gaps
Research or think through each gap
Gap 1: [Topic]
- The question: [What wasn't clear?]
- The answer: [What I learned]
- Now I can explain it as: [Simple version]
Step 4: Refined Explanation
Rewrite the complete explanation with gaps filled and simpler language
Final Simple Explanation
[The improved, complete explanation in plain language]
Improved Analogy
[A refined or new analogy that better captures the concept]
Key Takeaways
- [Core insight 1]
- [Core insight 2]
- [Core insight 3]
Test Question If someone asked me to explain this in 30 seconds, I'd say:
[Elevator pitch version]
Guidelines
- Don't pretend to understand—gaps are valuable
- Use analogies from everyday life
- If you need jargon, define it simply
- Shorter is usually better
- The "explain to a child" bar is high—take it seriously
$ARGUMENTS
More from neurofoo/agent-skills
socratic
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
102scamper
SCAMPER creative brainstorming with seven prompts—Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse. Use for innovation, product ideas, or breaking creative blocks.
61jtbd
Jobs to Be Done analysis to understand what customers really want. Use for product discovery, competitive analysis, or understanding why customers hire/fire solutions.
545whys
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.
46ooda
OODA loop decision framework (Observe, Orient, Decide, Act). Use for complex decisions, problem-solving, unclear situations, or when someone is jumping to solutions without analysis.
45redteam
Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect.
45