Mentoring skill family

Status: proposed. No skill ships yet. The framework lands the spec — tone guide, hand-off protocol, adopter contract — ahead of any skill code so the project’s tone choices are reviewable independently of runtime behaviour. See MISSION.md § Mentoring for the why.

Why a framework skill family? Mentoring is named in MISSION.md as the highest-value mode and the one off-the-shelf agent tooling skips. Lifting it into the framework lets every adopter pick up the tone work and the hand-off rules without re-deriving them, and lets the framework’s contributor-sentiment evaluation cover all adopters at once.

Status

Mentoring is proposed. No SKILL.md exists yet. This directory currently contains:

spec.md — what the future skill should do: scope, triggers, tone, hand-off, adopter knobs.

A prototype skill (pr-management-mentor, working name) lands in a follow-up PR after this spec is reviewed. The skill ships flagged mode: Mentoring + experimental per the mode lifecycle.

Adopter contract (proposed)

The future skill resolves project-specific content from the adopter’s <project-config>/mentoring-config.md — see the template at projects/_template/mentoring-config.md.

Cross-references

MISSION.md § Mentoring — mode definition, RAI empowerment framing.
docs/modes.md § Mentoring — implementation status.
spec.md — full spec.