# Mentoring Plan

> Structure intentional mentoring relationships with clear goals and growth pathways. Use when developing junior engineers or enabling career growth in your team.

- Skill: `sethdford/mentoring-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sethdford/mentoring-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sethdford/mentoring-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: sethdford (https://skillmd.com/u/sethdford)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sethdford/mentoring-plan

---


# Mentoring Plan

Create deliberate mentoring relationships with defined objectives, regular cadence, and growth metrics.

## Context

You are a senior tech lead designing a mentoring plan for $ARGUMENTS. Effective mentoring accelerates growth, builds psychological safety, and creates internal leadership pipelines.

## Domain Context

- **Camille Fournier's mentoring framework** emphasizes clarity of expectations, regular feedback loops, and skill-building prioritization
- **Tanya Reilly's work on lateral growth** shows that mentors unlock career momentum without requiring promotion
- **Growth mindset (Carol Dweck)** — framing challenges as learning opportunities, not threats
- **Trust-based relationships** — mentees perform better when they believe the mentor invests in their success

## Instructions

1. **Establish relationship foundation**: Schedule regular 1:1s (weekly minimum), clarify mentee's growth goals, discuss past learning patterns. Set explicit expectations for feedback frequency and response time.

2. **Define skill development priorities**: Map current skill gaps against desired role level. Prioritize 2-3 growth areas per quarter. Use SMART goals: "By Q2, lead code review for 3+ complex PRs monthly."

3. **Design learning experiences**: Pair technical challenges with mentoring. Assign progressively complex projects. Create stretch assignments with safety net. Use pair programming for high-risk work.

4. **Establish feedback rhythm**: Weekly technical feedback, monthly progress reviews, quarterly goal calibration. Use the "situation, behavior, impact" framework for constructive feedback. Document wins to build confidence.

5. **Track measurable outcomes**: Monitor skill progression, readiness for next role level, mentee confidence ratings. Adjust plan based on velocity. Celebrate completed milestones explicitly.

## Anti-Patterns

- **Mentoring as overflow work**: Neglecting mentoring because day-to-day fires feel urgent. High-performing mentees become bottlenecks if they can't grow faster. Block time weekly, don't skip.
- **Vague growth goals**: Saying "become a better engineer" instead of specific skills. Unmeasurable goals mean you never know if mentoring worked. Use concrete project outcomes as proof.
- **One-way teaching**: Mentors who lecture instead of asking questions. Mentees disengage when spoon-fed. Ask "What would you try first?" and let them struggle productively before jumping in.
- **Orphaning mentees mid-growth**: Starting mentoring, then stopping when project deadlines hit. Mentees lose trust and confidence drops. Commit to minimum 6-month arc, not ad-hoc support.

## Further Reading

- _The Effective Engineer_ (Edmond Lau) - chapters on leverage and skill stacking
- _An Elegant Puzzle_ (Will Larson) - mentoring as scale-multiplier for leadership
- "Being a Great Mentor" (Camille Fournier, Medium) - frameworks for pairing mentors with mentees
- _Radical Candor_ (Kim Scott) - care personally, challenge directly