Run stakeholder alignment

Skill alexe-ev/product-plugins/leadership-communication/skills/run-stakeholder-alignment

Plan and execute a stakeholder alignment process for a product decision or initiative. Use this skill when a team needs to build genuine alignment — not just sign-off — across multiple stakeholders.From its SKILL.md

Install

npx -y skills add alexe-ev/product-plugins --skill run-stakeholder-alignment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 501 tokens by cl100k_base, as published. Nobody here has run it

Run Stakeholder Alignment

Purpose

Help teams design and execute a structured alignment process that builds genuine shared understanding and commitment across stakeholders — not just surface-level approval.

Skill type

Conceptual skill

Use this skill when

A decision or initiative requires buy-in from multiple stakeholders who currently disagree
Alignment has been declared but keeps breaking down in execution
A cross-functional initiative needs to be aligned before resources are committed
A difficult conversation with a key stakeholder needs to be planned

Do not use this skill when

The goal is mapping stakeholders (use map-stakeholder-influence first)
The goal is executive communication content (use build-executive-narrative)

Required inputs

Decision or initiative requiring alignment
Stakeholders involved and their current stances

Optional inputs

Stakeholder map
Prior alignment attempts and what went wrong
Decision timeline
Key concerns or objections known in advance

Upstream context

Works best when:

Stakeholder map exists
Decision is defined
Options are prepared

Downstream handoff

Output can feed:

communicate-decisions-tradeoffs (aligned decision → communication)
build-executive-narrative (alignment informs narrative framing)

Instructions

Define the alignment goal: what specific agreement or understanding must be reached?
Identify who must align (vs. who just needs to be informed).
Map each stakeholder's current stance and known concerns.
Design the alignment sequence: who to engage first, in what order, through what format.
Prepare for each key conversation: their concerns, your response, what you're willing to adjust.
Define what success looks like (not just "they didn't object" — but genuine agreement on the key points).
Plan follow-up to confirm alignment holds.

Output

Provide:

Alignment goal
Must-align stakeholder list with stances
Engagement sequence
Preparation per key stakeholder: concerns, responses, negotiable elements
Success definition for alignment
Follow-up plan to maintain alignment
Contingency if alignment isn't reached

Risks / caveats

"No objections" is not alignment — ask stakeholders to restate their understanding
Stakeholders who feel steamrolled become active opponents — engage concerns genuinely
Alignment reached under time pressure is fragile — invest time early, not at the last moment

What ships with it: 4 files

9.5 KB alongside SKILL.md

examples/

Gives 0 of the 12 instructions most operations skills give in 501 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

Define the specific alignment goal
Separate who must align from who needs informing
Design the stakeholder engagement sequence
Prepare concerns, responses, and negotiable elements
Define specific success criteria for alignment
Plan follow-up to confirm alignment holds

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.