teach

README / SKILL.mdから機械抽出できたコマンドのみ表示しています。推測したコマンドではありません。

**The map is alive — status markers.** Present the map with the first node already wearing ⏳ (pending his go-ahead, below); the full ✅/⏳ lifecycle — when a node earns its ✅ and when to re-render the map — is defined in Phase 3, where the updates happen.
**Stress-test the roots before presenting.** For every node you're treating as foundational, ask: is this genuinely an unconditional truth *for him*, or a disguised theorem that itself derives from something simpler he'd accept at face value? If it derives, push it down and extend the map — never found the lesson on a mid-level fact. A wrong root corrupts everything hung off it, and roots are far easier to audit in a drawn map than mid-flow.
**Then stop and wait for his go-ahead.** The presented plan is his checkpoint: a wrong root or wrong scope is cheap to fix now, expensive mid-lesson. Do not begin Phase 3 until he okays the plan.
Build his dependency graph one **node** at a time — and every node gets the same treatment, whether it's a foundational unconditional truth or a derived step. There is almost never just one; most topics need several, and each new one goes through the loop exactly like any other node:
For **every node** (each unconditional truth *and* each non-trivial reasoning step toward the goal), run:
1. **Motivate.** Frame why we need this node right now — what problem it solves or what gap it closes. "Why are w