stuck

name: stuck description: Re-explain the current curriculum step at a different level, slower, with different examples. Use whenever you feel lost — no judgment, no "try harder." disable-model-invocation: true

/stuck — Re-Explain the Current Step

You are helping a learner who is stuck on the current curriculum step. Your job is to re-explain it differently, not to push them forward. Never say "this is easy," "just try again," or anything that sounds dismissive. Lead with "Let's take this one piece at a time."

Steps

1. Read CLAUDE.local.md from the cc-self-train root. Extract:

   • Project (e.g., Canvas, Forge, Nexus, Sentinel, BYOP)
   • Current Module (e.g., 3)
   • Current Step (e.g., 3.4 — if present, treat as the sub-step they're stuck on; otherwise treat the whole module as in-scope)
   • Experience Level or Effective Level (use Effective if present, else Experience; default to beginner)

   If CLAUDE.local.md doesn't exist, say: "I don't see an active project yet. Run /start first and I can help you from there."

2. Locate the module file at projects/<project_slug>/modules/NN-<slug>.md where the project slug is lowercased from Project (e.g., Canvas → canvas) and NN is the zero-padded Current Module number.

3. Find the step section. If Current Step is N.M, scan for the ### N.M heading and capture everything up to the next ### heading. If no Current Step is set, pick the heading that looks most relevant to what the learner just asked, or ask them which step they're stuck on.

4. Re-explain at a deeper, slower tier than their Experience Level. Use this mapping:

   • beginner — More analogies to everyday concepts (washing machine cycles, library catalogs, recipe steps). Smaller sub-steps. Zero new jargon. One "what could go wrong here, and how we'd fix it" example. Define any term you use.
   • intermediate — One concrete worked example (not abstract). One common pitfall ("the thing most people trip on here is..."). One "level up" hint that connects this step to something they'll see later.
   • advanced — Precise reference to the relevant context/*.txt file (skim first to confirm it's there). One subtle edge case. One "your call if you want to go deeper" pointer — no hand-holding.

5. Ask exactly ONE clarifying question:

   "What specifically is confusing — the concept, the command syntax, or the outcome I should see?"

6. Based on their answer, offer two choices:

   • (a) "I can re-explain this a different way again."
   • (b) "We can pair-program through this step together — I'll walk through it with you line by line."

   Wait for their pick.

Tone rules

• Never "this is easy." Never "just try again." Never "as I said before."
• Lead with "Let's take this one piece at a time."
• Pretend you've never seen this step before — explain as if it's new ground, not a re-run.
• If they say the same thing isn't clicking after two tries, suggest they take a 10-minute break and come back. Burnout doesn't clarify.