forced-feynman

Diagnose understanding gaps by challenging learner explanations of studied topics.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill forced-feynman-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forced-feynman
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/opencode/skills/learning/forced-feynman
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill forced-feynman-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learners often believe they understand a topic until they try to explain it. This Skill runs a Feynman-style teach-back session where the learner explains a recently studied topic in plain language, and the AI challenges jargon, missing causal steps, and misleading simplifications to expose real gaps in understanding. ## Core Features & Use Cases - Teach-back setup: Invites the learner to explain a topic as if to a curious ten-year-old, without giving a model answer first. - Claim-by-claim challenge: Breaks each explanation into claims, quotes the weakest phrase, and asks the learner to define terms, supply missing steps, or predict counterexamples. - Foundation report: Summarizes actual mistakes (missing definition, missing mechanism, boundary confusion, unsupported assumption), separates repaired from unresolved gaps, and asks one transfer question. - Use Case: After reading about how database indexes work, a learner explains the concept in their own words; the Skill catches that they skipped why a B-tree lookup is logarithmic and probes until they can articulate the mechanism. ## Quick Start Ask the AI to run a Feynman teach-back on a topic you just studied and challenge every gap in your explanation.

Frequently Asked Questions about forced-feynman

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the Feynman technique to test my understanding?

Explain the topic in plain language as if teaching a ten-year-old, one short paragraph per turn. The Skill breaks your explanation into claims, challenges jargon and missing causal steps, and waits for you to repair each gap before continuing.

How does teach-back learning find knowledge gaps?

Teach-back exposes gaps by forcing you to produce causal reasoning rather than recall facts. The Skill checks each claim for undefined jargon, missing mechanism steps, oversimplifications that change the rule, and correct conclusions reached through false mechanisms.

Can I use this to verify my understanding of a code repository?

Yes. For a named repository, the Skill inspects the relevant code and tests before judging your explanation, and cites verified file:line evidence in its feedback rather than relying on general impressions.

What are the limitations of explanation-based learning checks?

A single explanation cannot prove complete mastery, so the Skill never claims it. It ends with one new application question to test transfer, and if you stop early it reports the remaining uncertainty instead of inventing mistakes.

Does the Feynman method forbid technical terminology?

No. Technical words are allowed when you can explain what they mean. Plain language is a test of understanding, not a ban on accurate terminology, and harmless imprecision is not punished.