agentleFS
qingxuantangqingxuantang/Lennys-to-sop-and-skills/skills/leadership-coach/SKILL.md

leadership-coach

Skill16 starsChanged 10 months agoMITView on GitHub

Coaches on leadership, management, and team development. Use when: discussing management challenges, giving feedback, developing teams, deciding when to be hands-on, driving organizational change, or building leadership skills. Includes: Radical Candor, Selective Micromanagement, Managing Complex Change, Coaching Tree, Career Impact frameworks. Sources: Kim Scott, Ravi Mehta, Bangaly Kaba, Brian Chesky, Claire Hughes Johnson.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. TongyiDai/leadership-coach★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't defend immediately

    line 94
  2. Distinctive:

    No clear end in sight

    line 136
  3. Distinctive:

    Not having an exit plan

    line 173
  4. Distinctive:

    Only developing to Application

    line 282
  5. Distinctive:

    Not checking for progression

    line 283
  6. Distinctive:

    Not everyone needs to be LeBron

    line 304
  7. Distinctive:

    Keep relationships after people move

    line 336
  8. Distinctive:

    Leave if: Manager is the problem, multiple unfixable factors

    line 390
  9. Distinctive:

    Not talking to manager

    line 398

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Leadership Coach Skill

Help users become better leaders and managers using proven frameworks.

When This Skill Activates

  • "How do I give feedback?"
  • "Should I micromanage?"
  • "My team isn't executing"
  • "How do I develop my team?"
  • "Driving organizational change"
  • "Am I a good manager?"
  • "Career advice"
  • "Building leadership skills"

Framework Selection Guide

SituationUse This Framework
Giving difficult feedbackRadical Candor
Deciding how hands-on to beSelective Micromanagement
Team not executing, need changeManaging Complex Change
Developing team membersBloom's Taxonomy Coaching
Building leadership legacyCoaching Tree
Personal career growthCareer Impact Framework

Framework 1: Radical Candor

Source: Kim Scott - Lenny's Podcast Key Insight: Good feedback requires both caring personally AND challenging directly.

The 2x2 Matrix

Challenge DirectlyDon't Challenge
Care PersonallyRadical Candor ✓Ruinous Empathy
Don't CareObnoxious AggressionManipulative Insincerity

Radical Candor (Goal)

  • Care about the person
  • Challenge their work/behavior
  • Specific and actionable
  • Delivered with respect

Ruinous Empathy (Common Trap)

  • Care about person but avoid hard feedback
  • "I don't want to hurt their feelings"
  • Short-term kindness, long-term harm
  • Person never improves

Obnoxious Aggression

  • Challenge without caring
  • Brutal honesty without empathy
  • Creates fear, not growth

Manipulative Insincerity

  • Neither care nor challenge
  • Political, fake feedback
  • Worst of all quadrants

Delivering Radical Candor

Step 1: Establish You Care Build relationship first. Feedback lands better from someone who clearly cares.

Step 2: Be Specific Not: "Your presentations need work" Yes: "In yesterday's presentation, you lost the room when you went into technical details. The executives needed business impact first."

Step 3: Make It Actionable Include what to do differently.

Step 4: Do It Quickly Feedback decays rapidly. Give it within 48 hours.

Step 5: Do It Privately (Usually) Praise publicly, critique privately.

Receiving Feedback

  • Thank them for the feedback
  • Clarify to understand
  • Don't defend immediately
  • Reflect, then respond

Pitfalls to Avoid

  • Defaulting to Ruinous Empathy
  • Feedback without relationship
  • Being vague to soften it
  • Waiting too long

Framework 2: Selective Micromanagement

Source: Ravi Mehta - Lenny's Podcast Key Insight: Micromanagement isn't always bad—selective, temporary micromanagement is effective when your team is going in the wrong direction.

The Leadership 2x2

Team Has AutonomyTeam Lacks Autonomy
You're ConfidentScalable Leadership ✓Selective Micromanagement ✓
Not ConfidentHands-Off (Risky) ✗Micro-Mismanagement ✗

Scalable Leadership (Ideal State)

  • You're confident in direction
  • Team has autonomy
  • You've established frameworks
  • Team makes good decisions

Selective Micromanagement (When Needed)

  • You're NOT confident in direction
  • You temporarily reduce autonomy
  • You guide to right path
  • You pull back when aligned

Hands-Off (Failure Mode)

  • You're NOT confident but let them continue
  • "I don't want to micromanage"
  • Team goes off the rails

Micro-Mismanagement (Failure Mode)

  • Constant control
  • No clear end in sight
  • No autonomy ever
  • Everyone frustrated

Assessing Confidence Level

High Confidence:

  • Decisions align with strategy
  • They anticipate your concerns
  • Work product meets bar
  • You'd make similar choices

Low Confidence:

  • Decisions seem off-strategy
  • Surprised by their direction
  • Quality issues emerging
  • You'd make different choices

Executing Selective Micromanagement

Step 1: Be Transparent

"I noticed [concern]. I'm going to be more hands-on for a few weeks to help us get aligned."

Step 2: Get Tactical Get into specific decisions, not just strategy

Step 3: Teach Frameworks Share how you think, not just what to do

Step 4: Plan the Exit

  • Define what "aligned" looks like
  • Typically 2-6 weeks, not quarters
  • Move from directing to reviewing

Pitfalls to Avoid

  • Avoiding micromanagement when needed
  • Micromanaging without teaching
  • Not having an exit plan
  • Micromanaging when you're already confident

Framework 3: Managing Complex Change

Source: Bangaly Kaba - Lenny's Podcast Key Insight: Missing any single component produces a predictable failure mode.

The Five Components

ComponentPurpose
VisionWhere we're going
SkillsCapabilities to execute
IncentivesMotivation to do it
ResourcesPeople, budget, tools
Action PlanClear next steps

Missing Component → Failure Mode

MissingResult
VisionConfusion
SkillsAnxiety
IncentivesResistance
ResourcesFrustration
Action PlanFalse starts

Diagnostic Process

Step 1: Observe the Team

  • Sit in meetings, listen
  • Talk to people across functions
  • Note repeated conversations

Step 2: Match Symptoms to Missing Component

Confusion (Missing Vision):

  • "What are we trying to do?"
  • People pulling different directions

Anxiety (Missing Skills):

  • "I don't know how to do this"
  • Quality issues, avoidance

Resistance (Missing Incentives):

  • "Why should I care?"
  • Passive agreement, no follow-through

Frustration (Missing Resources):

  • "We don't have what we need"
  • Constant firefighting

False Starts (Missing Action Plan):

  • "We keep starting but not finishing"
  • Same discussions repeated

Step 3: Address the Right Component

Ease of change (easier → harder):

  1. Action Plan (quick tactical wins)
  2. Resources (if you have authority)
  3. Incentives (needs org support)
  4. Skills (takes time)
  5. Vision (hardest but most fundamental)

Pitfalls to Avoid

  • Jumping to solutions without diagnosis
  • Addressing only easy components
  • Trying to fix everything at once
  • Ignoring resistance (incentives)

Framework 4: Bloom's Taxonomy for Coaching

Source: Bangaly Kaba - Lenny's Podcast Key Insight: Identify where in the learning progression someone is stuck, then provide appropriate support.

The Six Levels (Basic → Advanced)

LevelDescriptionDiagnostic
KnowledgeCan recall facts/concepts"Tell me about X"
ComprehensionCan explain in own words"Why does X work?"
ApplicationCan use in specific situation"How have you used X?"
AnalysisCan apply across contexts"When would you use X vs Y?"
SynthesisCan create new approaches"How would you adapt X?"
EvaluationCan judge when to use what"When should we NOT use X?"

Matching Development to Level

Knowledge Gap → Reading, videos, definitions Comprehension Gap → Discussion, teach-back exercises Application Gap → Supervised practice, examples Analysis Gap → Multiple contexts, case studies Synthesis Gap → Novel problems, design exercises Evaluation Gap → Critique exercises, judgment calls

Manager Requirements by Level

  • ICs should reach Application for their scope
  • Managers must reach Analysis across their teams
  • Directors+ need Synthesis and Evaluation

Pitfalls to Avoid

  • Teaching at wrong level
  • Expecting immediate jumps
  • Only developing to Application
  • Not checking for progression

Framework 5: Coaching Tree Leadership

Source: Bangaly Kaba - Lenny's Podcast Key Insight: Your legacy is measured by who you developed, not what you shipped.

What is a Coaching Tree?

In basketball, the coaches who learned under you and went on to success. Same applies to product/tech leadership.

Your Tree Includes

  • Direct reports who became leaders
  • PMs who grew into senior roles
  • Engineers who became managers
  • People who say you changed their career

PM as Team Sport

  • You're the coach, not the star player
  • Success comes from team performance
  • Not everyone needs to be LeBron
  • Role players matter

Building Your Tree

Step 1: Know People by Name and Story

  • Professional background and aspirations
  • Personal life and what matters
  • Strengths and growth areas
  • Motivations and fears

Step 2: Identify Role Types

RoleValue
Star playerHigh-impact work
Reliable executorConsistent delivery
Culture carrierMaintains norms
Domain expertDeep knowledge
ConnectorCross-team relationships

Step 3: Coach Up, Not Out

  • Diagnose where they're stuck
  • Provide targeted development
  • Give stretch opportunities
  • Celebrate progress

Step 4: Delegate for Growth

  • Delegation is a gift of growth
  • Provide support proportional to stretch
  • Expect mistakes, use for learning

Step 5: Stay Connected

  • Keep relationships after people move
  • Celebrate their wins
  • Track where they went

Pitfalls to Avoid

  • Being the hero (doing all hard work yourself)
  • Only developing stars
  • Not staying connected
  • Measuring only your direct output

Framework 6: Career Impact Framework

Source: Bangaly Kaba - Lenny's Podcast Key Insight: Impact = Environment × Skills. Both must be strong.

The Formula

Impact = Environment × Skills

Great skills in bad environment = limited impact Great environment with skill gaps = limited impact

Environment Variables (Score 0-2)

  1. Manager (Most important) - Quality and support
  2. Resources - Team, budget, tools
  3. Scope - Size and importance of remit
  4. Team - Skills and dynamics
  5. Compensation - Fair and motivating
  6. Culture - Supportive environment

Skill Variables (Score 0-2)

  1. Communication (Most important) - Written, verbal, listening
  2. Influence - Building alignment without authority
  3. Strategic Thinking - Connecting to business outcomes
  4. Execution - Getting things done

Assessment Process

Step 1: Score Environment Rate each variable, identify low scores

Step 2: Score Skills Rate each, get manager/peer input

Step 3: Identify Limiting Factors Which scores are below 1.0?

Step 4: Assess Changeability Can you change it? How?

Step 5: Decide: Fix or Leave

  • Stay if: Low scores changeable, manager supportive
  • Leave if: Manager is the problem, multiple unfixable factors

Key Insight on Manager

"People don't leave jobs, they leave managers—because the manager has power to fix many variables."

Pitfalls to Avoid

  • Blaming only environment (skills matter too)
  • Blaming only yourself (environment matters)
  • Not talking to manager
  • Optimizing only for compensation

How to Apply This Skill

  1. Identify the leadership challenge
    • Feedback → Radical Candor
    • Team off-track → Selective Micromanagement
    • Change needed → Managing Complex Change
    • Developing someone → Bloom's Taxonomy
    • Leadership growth → Coaching Tree / Career Impact
  2. Walk through the relevant framework
  3. Help create specific action plan
  4. Check in on progress

Related Skills

  • /pm-coach - For PM-specific development
  • /decision-maker - For leadership decisions
  • /hiring-guide - For building teams

Full SOPs (Deep Dives)

Core Leadership

  • Radical Candor
  • Selective Micromanagement
  • Managing Complex Change
  • Bloom's Taxonomy Coaching
  • Coaching Tree
  • Career Impact

Founder & Executive

  • Founder Mode
  • Company Operating System
  • Personal Operating Principles
  • 100-Year Thinking
  • Technical Founder Leadership
  • Trust-Based Culture
  • Beginner's Mind

Emotional Intelligence

  • Fear/Anger Decision
  • Energy Audit
  • Creative vs Reactive Leadership

Difficult Conversations

  • Compassionate Firing
  • Large-Scale Layoffs

Culture Building

  • Culture Code Creation
  • Culture as Product

Engineering Leadership

  • Engineering Management Ladder
  • Manager to Manager-of-Managers
  • Skip-Level Meetings
  • Platform Teams
  • Staff Engineer Sponsorship
  • Engineering Strategy
  • EM-PM Partnership

Career Development

  • Career as Product
  • 30-60-90 Onboarding
  • Executive Coaching
  • Introverts Workplace Success

Personal Development

  • Radical Self-Inquiry
  • Leadership Authenticity
  • GENIE Goal Setting
  • Overcoming Imposter Syndrome

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.