stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
Security Assessment
About stakeholder-map
The stakeholder-map skill helps product and program leaders build a structured stakeholder map using a Power × Interest grid and turn it into a tailored communication plan. It solves the common problem of managing many parties with competing needs during launches, cross-functional alignment, or ongoing stakeholder engagement, replacing ad-hoc outreach with a deliberate strategy per group. The skill accepts context through $ARGUMENTS and can read supplied files such as org charts, project briefs, or team rosters, or infer likely stakeholders from a described product or initiative.
The workflow guides you through identifying all relevant individuals and groups (executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, end users), classifying each on Power (High/Low) and Interest (High/Low), and placing them into the four grid quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor. For each quadrant it recommends communication frequency (daily, weekly, bi-weekly, monthly), format (1:1, email, Slack, meeting, dashboard), key messages and framing, and the risks of neglecting that group. It then produces a communication plan table with columns for Stakeholder, Role, Power, Interest, Strategy, Frequency, Channel, and Key Message, and flags stakeholders with competing interests along with alignment strategies.
This skill targets product managers, program managers, and cross-functional leads preparing for launches or aligning teams. The output is saved as a markdown document. It is a reasoning and documentation aid rather than an integration with external tooling, so its value depends on the quality of the context and files provided. The skill points to further reading including the Product Management Frameworks Compendium and a Team Topologies handbook.
FAQ
What framework does this skill use to map stakeholders?
It uses a Power × Interest grid with four quadrants: Manage Closely (high power, high interest), Keep Satisfied (high power, low interest), Keep Informed (low power, high interest), and Monitor (low power, low interest).
What do I need to provide to get a good result?
You pass the initiative via $ARGUMENTS. You can also provide files such as org charts, project briefs, or team rosters, which the skill reads first. If you only describe the product or initiative, it will infer likely stakeholders from that context.
What does the final output look like?
A markdown document containing the stakeholder classifications, per-quadrant communication recommendations, and a communication plan table with columns for Stakeholder, Role, Power, Interest, Strategy, Frequency, Channel, and Key Message, plus flagged conflicts and alignment strategies.
When should I use this skill?
Use it when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
Does it recommend how often to communicate with each group?
Yes. For each quadrant it suggests a communication frequency (daily, weekly, bi-weekly, or monthly) and a format such as 1:1, email, Slack, meeting, or dashboard, along with key messages and neglect risks.
Install stakeholder-map
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
phuryn/pm-skills