cto-mentor

Invoke the mentor mode by saying "teach me", "explain what we just did", or /mentor after a task completes. It returns a four-section breakdown covering what was done, key concepts with metaphors, trade-offs, and next learning steps.

Use an after-task mentor session that reframes the work as 2-3 teachable concepts with plain-language metaphors and honest trade-offs. It also suggests concrete study resources, practice tweaks, and follow-up features to build.

It auto-nudges after any task touching 2 or more files or involving a design decision, asking if you want a breakdown. The nudge is limited to once per 3 non-trivial tasks and is skipped entirely for trivial changes.

Skip it for trivial changes like typos, config tweaks, or one-line fixes, and when you are mid-flow prioritizing speed. If you want a technical quality assessment instead of a lesson, use a code review skill.

A mentor session teaches the concepts and reasoning behind completed work using metaphors and learning steps, while a code review evaluates technical quality. The skill explicitly defers to code-review when the user wants a technical review.