feynman-walkthrough

Guides understanding-first walkthroughs of codebases, papers, and systems with persistent OKF explainers.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/dhanesh/agent-skills --skill feynman-walkthrough-dhanesh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feynman-walkthrough
Source: https://github.com/dhanesh/agent-skills/tree/main/feynman-walkthrough
Command: npx skills add https://github.com/dhanesh/agent-skills --skill feynman-walkthrough-dhanesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Explaining an unfamiliar codebase, whitepaper, or complex system well is hard: explanations drown learners in jargon, skip the big picture, and vanish when the chat session ends. This Skill runs a structured walkthrough that builds genuine understanding and persists it as a reusable reference explainer. ## Core Features & Use Cases - Guided walkthroughs: Scopes the learner's goal, presents a big-picture map, then explains one segment at a time using plain language, analogies, and concrete examples before abstraction. - Post-walkthrough understanding checks: Asks a few targeted questions after exposure to find shaky segments and re-explains them from a different angle until they land. - Persistent OKF knowledge bundles: Saves the explainer as an Open Knowledge Format bundle with source fingerprints pinned (git HEAD or sha256), so later sessions can detect drift and refresh diff-aware. - Use Case: Onboard a new engineer onto a repository: the Skill tours one real code path end-to-end with file:line citations, surfaces design rationale, and writes a standalone explainer into docs/knowledge/ that stays fresh-checkable as the code evolves. ## Quick Start Ask the agent to walk you through this repository using the feynman-walkthrough skill and save the explainer for future sessions.

Frequently Asked Questions about feynman-walkthrough

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

FAQPage Schema
How do I onboard someone onto an unfamiliar codebase with an AI agent?▼

Run a codebase walkthrough that maps the components, traces one real execution path end-to-end with file:line citations, and surfaces design rationale from git history and ADRs. The session ends with a standalone explainer document the next onboarder can read directly.

What is the Feynman technique for explaining complex topics?▼

The Feynman technique explains each idea in plain language with concrete examples before introducing terminology, and treats any jargon or glossed step as a gap in the explanation. This Skill applies that standard to the explainer, not as a quiz burden on the learner.

Does the walkthrough require Python or a specific environment?▼

The walkthrough itself works in plain conversation with no dependencies. Persisting explainers as OKF bundles and generating spaced-review schedules requires python3 with the standard library only; git is optional and used to fingerprint repository sources.

How does the explainer stay current when the codebase changes?▼

Each OKF explainer pins a fingerprint of its sources, such as git HEAD or a file sha256. Running okf.py status reports FRESH, STALE, or UNKNOWN, and okf.py diff lists exactly which files changed so only affected segments get refreshed.

Does this skill force quizzes or spaced repetition on learners?▼

No. Understanding checks come only after the walkthrough to steer coaching, and retention tooling like spaced retrieval schedules is strictly opt-in. The default deliverable is the walkthrough plus the reference explainer.