ask-lonlydwolflisted

# Ask lonlydwolf ## The door test **Is this one subject, or a journey through several?** - **One subject** — nameable in one breath ("Rust lifetimes", "how DNS works") → **Matt's `/teach`**, right where you are. No course folder, no `/setup-faculty-skills`; its mission step does the scoping. - **A journey** — a field, a curriculum-sized ambition, anything you'd describe with a syllabus → the main flow below. **When unsure, pick `/teach`** — mis-picking small is safe (the tripwire below catches it); mis-picking big buys planning overhead a single subject never repays. `/teach` is Matt Pocock's and nothing here installs it: `npx skills@latest add mattpocock/skills`. ## The main flow: subject → course 1. **Make a folder** — one course per folder; every session runs from its root. 2. **`/setup-faculty-skills`** — once: scaffolds the workspace and the learner profile, settles the theme. 3. **`/academic-advisor`** — the mission run; creates the roadmap. 4. **The loop**: `/academic-advisor` plans a unit ⟷ `/teach-unit` teaches it → `/audit` checks it → back to `/academic-advisor`, until the roadmap says *arrived*. A `/teach-unit` that ends suspended (`gap` or `over-budget`) goes back to `/academic-advisor` — the advisor owns the reroute. The goal itself moved? → `/academic-advisor` — the goal-shift run. Only you can fire it; no role ever infers a new destination. **The tripwire.** If `/teach`'s mission conversation sprawls into "this is really six subjects", exit: start th