coaching-pms

Frameworks for developing and coaching product managers using proven practices from top-company leaders.

refoundai/lenny-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

616

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/refoundai/lenny-skills --skill coaching-pms

0

installs

0

this week

616

stars

What it does

  • Establishes competency models and definitions of \"good\" before attempting to develop any PM, ensuring coaching is contextual to company stage and needs

  • Uses Bloom's Taxonomy to diagnose where PMs fall on the critical thinking spectrum (knowledge through evaluation) and targets development accordingly

  • Provides a five-step coaching framework: define success, assess current state,

Category

Productivity

Last updated

Apr 8, 2026

Installation Guide

How to use coaching-pms on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add coaching-pms
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill coaching-pms

Fetches coaching-pms from refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/coaching-pms

Restart Cursor to activate coaching-pms. Access via /coaching-pms in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

Coaching Product Managers

Help the user develop and coach product managers using frameworks from 3 product leaders who have scaled PM organizations at top companies.

How to Help

When the user asks for help with coaching PMs:

  1. Define "good" in context - Establish what a successful PM looks like for their specific company and stage
  2. Assess current state - Help diagnose where the PM is today across key competencies
  3. Create a shared vision - Align on what growth looks like for both the PM and the organization
  4. Build a development plan - Design specific actions, feedback loops, and timelines

Core Principles

Define good before coaching

Petra Wille: "Step number one is really having a solid definition of what a good product person looks like in your context." Create explicit competency frameworks before attempting to develop anyone.

Use Bloom's Taxonomy for diagnosis

Bangaly Kaba: "Bloom Taxonomy describes what's the different levels or order of critical thinking... knowledge, comprehension, application, analysis, synthesis, and evaluation." Assess where PMs fall on the learning ladder to target development appropriately.

Coaching is the primary leadership job

Marty Cagan: "Sundar at Google has been saying that the number one thing they look for in their leaders is a good coach." Top companies (Google, Apple, Microsoft) prioritize coaching ability over domain expertise in their leaders.

Follow the 5-step framework

Petra Wille outlines a specific development process:

  1. Definition of Good - What does success look like here?
  2. Current Assessment - Where is the PM today?
  3. Shared Vision - Where do they want to be?
  4. Development Plan - What specific actions will get them there?
  5. Follow-up - How will you track and support progress?

Questions to Help Users

  • "What does a 'great' PM look like at your company specifically?"
  • "Which competencies are most critical for your current stage?"
  • "Where is this PM on the knowledge-to-evaluation spectrum?"
  • "What's the biggest gap between their current state and your needs?"
  • "How much of your time as a leader goes to coaching versus doing?"

Common Mistakes to Flag

  • Coaching without a competency model - Development is aimless without a clear definition of good
  • Treating all PMs the same - Junior PMs need different coaching than senior PMs
  • Focusing on weaknesses only - Great coaching amplifies strengths while managing around weaknesses
  • Delegating coaching to HR - PM development must come from PM leaders who understand the craft
  • Skipping the follow-up - Development plans without accountability rarely produce results

Deep Dive

For all 3 insights from 3 guests, see references/guest-insights.md

Related Skills

  • Running Effective 1:1s
  • Having Difficult Conversations
  • Delegating Work
  • Managing Up

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.563 reviews
  • M
    Meera FloresDec 28, 2024

    Solid pick for teams standardizing on skills: coaching-pms is focused, and the summary matches what you get after install.

  • Z
    Zara AbbasDec 28, 2024

    Registry listing for coaching-pms matched our evaluation — installs cleanly and behaves as described in the markdown.

  • G
    Ganesh MohaneDec 24, 2024

    coaching-pms reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Z
    Zara GuptaDec 12, 2024

    I recommend coaching-pms for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • D
    Dev HaddadDec 8, 2024

    Registry listing for coaching-pms matched our evaluation — installs cleanly and behaves as described in the markdown.

  • K
    Kabir VermaNov 27, 2024

    Useful defaults in coaching-pms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • M
    Meera RamirezNov 27, 2024

    coaching-pms fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Y
    Yash ThakkerNov 23, 2024

    We added coaching-pms from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • A
    Arya FloresNov 19, 2024

    coaching-pms is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • K
    Kabir ReddyNov 19, 2024

    Useful defaults in coaching-pms — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 63

1 / 7

Discussion

Comments — not star reviews
  • No comments yet — start the thread.