stakeholder-alignment

refoundai/lenny-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill stakeholder-alignment
0 commentsdiscussion
summary

Help users achieve stakeholder alignment using frameworks from 88 product leaders.

  • Guides users through understanding stakeholder motivations, structuring pre-alignment conversations, and preparing for objections using the \"Most Obvious Objections\" framework
  • Emphasizes presenting multiple options with trade-offs and a clear recommendation, rather than single proposals that invite criticism
  • Teaches core principles including distinguishing disagreement from misunderstanding, building
skill.md

Stakeholder Alignment

Help the user achieve stakeholder alignment using frameworks and insights from 88 product leaders.

How to Help

When the user asks for help with stakeholder alignment:

  1. Understand the situation - Ask who the stakeholders are, what decision needs to be made, and where resistance is coming from
  2. Identify motivations - Help them understand what each stakeholder cares about and their definition of success
  3. Structure the approach - Guide them on pre-alignment, communication sequence, and how to present options
  4. Prepare for objections - Help anticipate the Most Obvious Objections (MOOs) and prepare responses

Core Principles

Understand how they think, not what they think

Hilary Gridley: "What's more helpful than understanding what your CEO thinks is understanding how your CEO thinks." Analyze recurring themes in a leader's feedback to translate it into actionable principles rather than chasing specific opinions.

Present options with a recommendation

Matt LeMay: "Options and a recommendation is the magic formula. When you present a single option, people just start poking holes." Always present at least three options with clear trade-offs and a specific recommendation to encourage constructive discussion.

Get pre-alignment on strategy

Shreyas Doshi: "If you have a real product strategy that everybody is aligned with, a lot of the nonsense we do with annual planning goes away." Secure alignment on strategy before formal planning seasons to prevent endless friction.

Approach disagreements with curiosity

Ami Vora: "She would respond, 'Fascinating, you have to tell me more why you think that.'" When you hear an idea you strongly disagree with, assume the other person has information you don't have yet.

Distinguish disagreement from misunderstanding

Tomer Cohen: "Are you disagreeing or misunderstanding? If misunderstanding, let's spend the time. If disagreeing, let's stop wasting time arguing." Ask the other party to articulate your point of view in their own words to verify understanding.

Trust is built through consistency

Ian McAllister: "Trust is the currency of a product leader. Trust is built by repeatedly setting and meeting expectations." Tell the truth, launch what and when you said, and own mistakes immediately.

Use concentric circles for communication

Lulu Cheng Meservey: "Go out in concentric circles. Each circle assumes the inner circle knows better." Never skip a circle in the communication sequence (Team -> Stakeholders -> Leadership -> External).

Repeat messages relentlessly

Zoelle Egner: "I repeated the same three talking points 5,000 times. You just have to get used to saying the same stuff." Act as 'repeater-in-chief' across multiple formats because people require multiple exposures to internalize a message.

Learn the business constraints

Marty Cagan: "You have to know how it's marketed, how it's sold, how it monetizes. You have to convince stakeholders you understand what the issues are." Build trust by demonstrating deep understanding of legal, finance, sales, and compliance constraints.

Frame requests as trade-offs

Wes Kao: "I can design this PDF for you. That means the page redesign will have to wait until later this week." When asked for new tasks, explicitly state what current work will be deprioritized rather than saying yes or no.

Questions to Help Users

  • "What does success look like specifically for this stakeholder - what do they care about most?"
  • "Have you identified the 'gatekeepers' who need 1:1 alignment before the broader meeting?"
  • "What is the Most Obvious Objection you expect, and how will you address it?"
  • "Are there repeated disagreements that signal an unaligned strategy rather than a tactical issue?"
  • "How will you communicate this across different modalities (written, verbal, visual)?"
  • "What trade-offs are you asking them to accept, and have you been explicit about them?"

Common Mistakes to Flag

  • Presenting a single option - This invites criticism; always present multiple options with trade-offs
  • Skipping pre-alignment - Treating buy-in as a single high-stakes meeting rather than a collaborative journey
  • Framing as pushback - Thinking of disagreement as conflict rather than a constructive effort to align on business success
  • Assuming one communication is enough - Messages need to be repeated across multiple channels and formats
  • Not understanding motivations - Trying to align someone without knowing what they personally care about and fear

Deep Dive

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

Related Skills

  • Written Communication
  • Giving Presentations
  • Running Effective Meetings
  • Managing Up
how to use stakeholder-alignment

How to use stakeholder-alignment 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 development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add stakeholder-alignment
2

Execute installation 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 stakeholder-alignment

The skills CLI fetches stakeholder-alignment from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/stakeholder-alignment

Reload or restart Cursor to activate stakeholder-alignment. Access the skill through slash commands (e.g., /stakeholder-alignment) or your agent's skill management interface.

Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

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

Installation Steps

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.871 reviews
  • Anika White· Dec 12, 2024

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

  • Kiara Abbas· Dec 8, 2024

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

  • Diego Perez· Nov 27, 2024

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

  • Yash Thakker· Nov 19, 2024

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

  • Michael Ramirez· Nov 3, 2024

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

  • Valentina Bhatia· Oct 22, 2024

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

  • Maya Mensah· Oct 18, 2024

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

  • Dhruvi Jain· Oct 10, 2024

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

  • Maya Rahman· Sep 25, 2024

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

  • Anaya Jain· Sep 13, 2024

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

showing 1-10 of 71

1 / 8