stakeholder-engagement-advisor skill
Plan engagement for a specific stakeholder. Use when preparing an outreach, navigating resistance, or aligning a critical relationship before a key milestone.
Is the stakeholder-engagement-advisor skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the stakeholder-engagement-advisor skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills mkdir -p ~/.claude/skills cp -r /tmp/Product-Manager-Skills/skills/stakeholder-engagement-advisor ~/.claude/skills/stakeholder-engagement-advisor
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Stakeholder Engagement Advisor
Purpose
Plan how to engage a specific stakeholder — before a critical conversation, milestone, or relationship repair. Generic stakeholder engagement fails because it treats all stakeholders with the same message, medium, and cadence. An executive sponsor who privately disagrees with your direction needs different handling than an impacted frontline user who's never been consulted. This skill diagnoses the specific stakeholder relationship you're managing and delivers a tailored engagement approach that accounts for both sides of the conversation — their motivations and yours.
Run this skill once per priority stakeholder. Priority stakeholders are those in the "manage closely" quadrant from stakeholder-mapping, every Q1 (high-impact, low-power) stakeholder regardless of Power × Interest placement, and anyone who has the potential to block, delay, or fundamentally reshape your initiative.
Input
Works best with: The specific stakeholder and the situation — the conversation, milestone, or tension you're preparing for. Also useful: Their power/interest read, history with you or the initiative, and what a good outcome looks like.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The advisor opens by asking who the stakeholder is and what's coming up with them.
Example invocation: Plan engagement: our VP Sales publicly supports the replatform but keeps escalating exceptions — QBR in 2 weeks.
Key Concepts
Stakeholder Motivations vs. Your Motivations — The most common engagement failure is planning only your side of the conversation. Effective stakeholder engagement requires mapping what the stakeholder needs, wants, and fears — separately from what you need from them. Where these overlap, you have an alignment path. Where they diverge, you have a negotiation to prepare for.
Proxy — A credible representative who speaks for or stands in for a stakeholder who is hard to reach, part of a large group, or represents a community rather than an individual. A good proxy is validated: they understand and can speak for the people they represent. A convenient proxy — the person who shows up to meetings — often cannot. Name the proxy explicitly and verify their representativeness before relying on their input.
Analysis Before Action — The engagement plan has two phases: diagnosis (who is this person, what drives them, what is the relationship history?) and planning (what will you say, through which medium, with what desired outcome?). Teams that skip directly to planning produce tactics without foundation — a message crafted for the wrong motivation, a medium that signals the wrong level of importance, an ask that misreads what the stakeholder actually controls.
Equity Lens in Engagement — High-impact, low-power stakeholders (Q1 from stakeholder-mapping) require proactive engagement design, not an open-door policy. An open door serves the people who already know they have a seat at the table. Q1 stakeholders typically need you to go to them: structured research recruitment, named roles in review processes, and deliberate inclusion in decisions that affect them.
Next Action Commitment — Every engagement plan must end with a named next action: who does what, by when, through which medium, with what key message and desired outcome. Engagement plans without this commitment are intentions, not plans. The next action is the only part that actually moves the relationship forward.
Engagement Context — The situational frame around the engagement matters as much as the stakeholder profile. Preparing for a first contact requires different framing than recovering from a conflict, securing buy-in before a launch, or maintaining an already-aligned relationship. The context shapes the message, the medium, and the desired outcome.
Application
This skill runs as a guided conversation. Answer each question; the advisor synthesizes your inputs and delivers a tailored engagement plan structured around three decision points:
- Stakeholder profile — who they are and what role they play
- Power and impact — how much authority they hold vs. how much they're affected
- Engagement context — the situation you're preparing for
After all three, you receive a set of numbered engagement approaches to choose from, then a specific action plan.
Opening
"We're going to plan your engagement with a specific stakeholder. I'll ask three questions about them and the situation, then deliver a tailored approach — message framing, medium, cadence, and your next action.
Who is this stakeholder? Give me their name, role, and one sentence on the history of your relationship with them so far."
Question 1 of 3 — Stakeholder profile
"Which of the following best describes this stakeholder?
1. Executive sponsor or senior decision-maker — holds formal authority over scope, budget, or go/no-go; your initiative needs their active support or at minimum their absence of resistance
2. Cross-functional peer or partner — adjacent team lead whose capacity, systems, or process your initiative touches; peer relationship, not a reporting one
3. End user or community representative — the person or group who will live with the product's outcomes daily; may have limited org power but high stakes in the result
4. Skeptic or potential blocker — has publicly or privately expressed resistance, doubt, or competing priorities; could slow or derail the initiative if not addressed
5. Newly identified stakeholder — discovered mid-initiative; relationship history is thin or nonexistent"
Based on the answer, tailor the next question and the eventual recommendation.
Question 2 of 3 — Power and impact profile
"Looking at this stakeholder's position from your stakeholder mapping — or your best read if you haven't mapped formally yet:
1. High power, high impact — they can shape the initiative AND they're significantly affected by its outcome (e.g., the VP whose team's workflow changes and who controls the budget)
2. High power, low impact — they control resources or approval but aren't significantly affected day-to-day (e.g., a CFO approving budget for a product they'll never use)
3. Low power, high impact — they're directly affected by the product's outcome but have limited org authority to shape it (e.g., frontline users, support agents, end communities)
4. Low power, low impact — limited stakes and limited authority; still worth mapping but engagement investment should be proportionate"
Question 3 of 3 — Engagement context
"What's the situation you're preparing for?
1. First contact — establishing a relationship and earning credibility before the work gets political
2. Pre-milestone alignment — roadmap review, launch gate, OKR commitment, or exec briefing coming up; you need this stakeholder in a good place beforehand
3. Resistance or conflict — the stakeholder has expressed disagreement, is blocking progress, or has competing priorities that put them at cross-purposes
4. Elevating an underrepresented voice — this is a Q1 stakeholder who has been excluded from or underrepresented in decision-making; you're designing proactive inclusion
5. Ongoing maintenance — an existing, aligned relationship that needs sustained investment to stay that way"
Synthesis and recommendations
After all three answers, deliver a tailored engagement plan:
"Based on [stakeholder type], [power/impact profile], and [engagement context], here are your recommended approaches:
1. [Approach name] — [When this fits and what it accomplishes]
2. [Approach name] — [Alternative for different risk tolerance or timeline]
3. [Approach name] — [Option for higher or lower relationship investment]
Choose a number, combine approaches (e.g., '1 then 3'), or describe your situation in more detail."
After selection, deliver the specific plan:
- Key message: What is the single most important thing you want them to understand or believe after this interaction?
- Framing: How does this initiative connect to what they care about? Lead with their goals, not yours.
- Medium and format: Email, 1:1, group briefing, written pre-read, working session, or research participation? Why this medium for this stakeholder?
- Cadence: One-time touchpoint or recurring? At what frequency?
- What you need from them: Be specific — a decision, an approval, information, validation, or simply awareness.
- What they likely need from you: Based on their profile — transparency, influence over design, credit for contribution, assurance about risk, or proof of impact.
- Next action: [Owner] will [action] via [medium] by [date/milestone], with the message "[key message]" and the desired outcome "[what success looks like for this interaction]."
Handling edge cases
- If the stakeholder is a large group (e.g., a user community): shift to proxy identification — name the most credible representative, validate their alignment to the group, design engagement through them while building broader touchpoints over time.
- If the relationship has history of conflict: lead with listening before proposing; the goal of the first engagement is to understand their concerns, not to persuade.
- If the engagement plan feels implausible given timeline or access constraints: scope down to what's achievable and name the residual risk explicitly.
Examples
Sample conversation flow — Executive sponsor, pre-milestone
Advisor: "Who is this stakeholder?"
User: "SVP of Product — she's the exec sponsor. We've had two brief introductions at all-hands. She's publicly supportive but we've never had a real conversation about what she actually thinks about the approach."
Advisor: "Which profile fits best: 1-5?" [see Question 1]
More skills from deanpeters/Product-Manager-Skills
- Aacquisition-channel-advisorEvaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
- Aagent-orchestration-advisorDesign multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
- Aai-shaped-readiness-advisorAssess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
- Aaltitude-horizon-frameworkUnderstand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
- Aansoff-matrixMap evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.
- Aautonomous-investigationThe protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.
- Abattle-card-builderResearch and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
- Abusiness-health-diagnosticDiagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
- Acompany-intelResearch a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
- Acompany-researchCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
- Acompetitive-analysis-processOrchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.
- Acompetitive-intel-watchScheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.