repo-teacher

Repo Teacher

Run a codebase as a reverse classroom: the repo is the textbook, the learner is known, and the agent writes curriculum that bridges the two.

Four phases

1. Assess (/assess-learner) — capture the learner's background, known tech, gaps, objectives, time budget, and preferred style. Output: teaching/learner-profile.md.
2. Plan (/plan-curriculum) — analyse the repo, match its demands to the learner profile, produce a sequenced teaching plan. Output: teaching/curriculum.md.
3. Teach (/write-lesson) — materialise individual lessons with real code excerpts, explanations, exercises, and self-check questions. Output: teaching/lessons/NN-*.md.
4. Answer (/qa-mode) — interactive Q&A grounded in the source, calibrated to the profile.

When to use which phase

• If no teaching/ directory exists → start with /assess-learner.
• If profile exists but no curriculum → run /plan-curriculum.
• If curriculum exists and the learner asks "where do I start" → either begin writing Lesson 1, or switch to Q&A mode if they prefer exploratory learning.
• If the learner asks a direct question about the repo → Q&A mode is the right surface even mid-curriculum.

Non-negotiables

• Ground every technical claim in real source. File paths + line ranges + actual excerpts. No paraphrased code passed off as real.
• Calibrate to the profile. Don't explain concepts the learner already knows. Don't hand-wave concepts they don't.
• Stay honest about the limits of your analysis. If the repo is doing something you can't explain from reading it, say so.
• Respect the time budget. A finished 6-hour curriculum beats an abandoned 20-hour one.

Not what this skill is for

• Not for generating marketing/tutorial content about a repo (use a docs-generation plugin).
• Not for reviewing code quality (different task).
• Not for writing new code in the repo — this is pedagogy, not development.