Agent skill · product strategy · borghei
stakeholder-map
Map stakeholders by power × interest and design a communication plan that prevents surprise objections. Use when launching a major initiative, navigating an enterprise deal, planning a re-org, or pre-empting resistance to a roadmap change.
Why this skill is useful
Provides a structured stakeholder mapping process and engagement plan that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Stakeholder Map A 2x2 grid of stakeholders, plus a tactical engagement plan derived from the map. Used to pre-empt resistance, route decisions correctly, and match communication cadence to influence. When to use this skill Major initiative launch (re-platform, pricing change, market expansion) Enterprise deal navigation (multiple buying-committee members) Org re-design / re-org planning Roadmap change affecting multiple stakeholders Pre-board / pre-exec strategic decisions Post-mortem stakeholder map (who didn't we engage that we should have?) The 2x2: Power × Interest Low Power High Power ----------------- -------------------- ---------------------- High Interest Keep informed Manage closely Low Interest Monitor Keep satisfied Quadrants Manage closely (HP/HI): key decisions; influence + engaged. Highest investment. Keep satisfied (HP/LI): authority but not engaged. Don't let them surprise you. Keep informed (LP/HI): advocates and detractors who care. Use them. Monitor (LP/LI): light touch. Clarify First Before mapping, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] The initiative being mapped — the specific launch/deal/re-org/roadmap change (defines who counts as a stakeholder at all, Step 1) [ ] Each stakeholder's power source — hierarchy vs veto vs budget vs domain expertise (a compliance lead may outrank a VP; drives the Power axis in Step 2) [ ] Each stakeholder's stance — champion → supporter → neutral → skeptic → blocker (drives Step 3 and the conversion plans in Step 6) [ ] Decision/launch deadline — when the verdict lands (sets engagement cadence per quadrant, Step 5) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. Workflow Step 1 — List all stakeholders Brainstorm: Executive sponsors Decision-makers Influencers Implementers Users / customers Adjacent teams External parties (vendors, regulators, partners) Don't filter yet. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/stakeholder-map