tutor-path

Tutor Path

This skill renders the learning path for a tutoring topic — the ordered list of prerequisite concepts with progress markers and dependency annotations. Per design decision D2, the path is generated internally by /tutor-start and kept hidden unless the user explicitly asks to see it; this skill is how they ask.

The format is the "with dependencies" format chosen in D2:

Path for python-decorators (6 concepts):

  [✓] 1. closures
  [✓] 2. first-class functions
  [→] 3. wrapper functions          (needs: 1, 2)
  [ ] 4. @ syntax                   (needs: 3)
  [ ] 5. decorators with arguments  (needs: 3, 4)
  [ ] 6. real-world patterns        (needs: 4, 5)

State markers:

• [✓] — acquired (passed the two-application rule)
• [→] — currently being taught
• [ ] — pending (not yet started)

---

Step 0 — Resolve the target topic

STATE="$CLAUDE_PLUGIN_ROOT/scripts/state.sh"

0a. Subject resolution

If the user provided an argument (e.g., /tutor-path python-decorators), use it as the slug.

If no argument, prefer the in-progress topic. If multiple, ask:

ACTIVE=$(bash "$STATE" get '[.topics | to_entries[] | select(.value.status == "in_progress") | .key]')
ACTIVE_COUNT=$(echo "$ACTIVE" | jq 'length')

• 0 in-progress, 0 completed: "No topics yet. Run /tutor-start <subject> to begin one." Exit.
• 0 in-progress, ≥1 completed: ask which completed topic, or suggest /tutor-status for the overview. Exit.
• 1 in-progress: use that slug.
• multiple in-progress: ask "Which topic's path? [list slugs]"

0b. Validate

EXISTS=$(bash "$STATE" get ".topics[\"$SLUG\"] // null")

If EXISTS is null, tell user: "No topic named $SLUG. Run /tutor-status to see what you've started." Exit.

---

Step 1 — Render the path

Read the concepts array and render each one with its status marker and dependency annotation. The rendering is a bash loop — clearer than one giant jq expression and easier to debug if any field is missing.