Feynman technique coach

Explain a concept in your own words and get precise feedback on gaps, jargon and shaky logic.

Prompt template
Coach me using the Feynman technique. The concept: {{concept}}. I am studying at: {{level}}.

Process:
1. I will explain the concept in my own words below, as if teaching a beginner.
2. Review my explanation and report: (a) what is correct and clear, (b) errors or misconceptions, (c) places where I used jargon or hand-waving instead of explaining, (d) steps in the logic I skipped.
3. Give me a score from 1 to 5 for accuracy and for clarity, each with one sentence.
4. Ask me three targeted follow-up questions that probe my weakest spots, as a curious beginner would.
5. Show a tightened model explanation of about 120 words, but only after listing my gaps, so I can fix them first.

Be kind but exact. Do not add facts I did not claim just to be helpful, and flag anything where you are less than sure. If you are unsure about a fact, say so plainly. Never invent citations, quotes, statistics or URLs.

My explanation:
{{explanation}}
Example output
**Correct and clear:** the "shared list" framing and the idea that each block holds a fingerprint (hash) of the previous block. That chaining is exactly why tampering is detectable. **Errors:** "every few minutes" is true of some chains, not all. Block timing varies by design. **Jargon and hand-waving:** "fingerprint" is never explained: what makes it change if one character changes? Also missing: who keeps copies of the list and who agrees a block is valid. **Skipped steps:** why breaking later blocks is hard in practice (agreement among many participants, cost of rewriting). **Scores:** accuracy 4/5, clarity 3/5. **Follow-ups:** (1) Who decides which block is added next? (2) What if two people add a block at the same moment? (3) Why can't someone just recalculate all the later fingerprints? **Tightened model:** A blockchain is a ledger copied across many computers. Transactions are bundled into blocks, and each block stores a hash of the one before it, so altering history changes every later hash. Because all participants hold copies and follow agreed rules for accepting new blocks, a forged history is quickly rejected.

Why it works

Feedback before the model answer is the point: fix your own gaps first, then compare. Repeat with your revised explanation until the scores reach 5.

Licensed CC0 (public domain) Version 1 · history