MaVoid-Team/stakeholder-map
Agent-Skills/PM-Skills/skills/stakeholder-map/SKILL.md
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.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add MaVoid-Team/Capital-Consultancy-Final stakeholder-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 3:35 PM339.9s1 file scanned
SKILL.md
- name:
- stakeholder-map
- description:
- 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.
Stakeholder Mapping & Communication Plan
Map stakeholders on a Power × Interest grid and create a tailored communication plan for each group.
Context
You are helping build a stakeholder map for $ARGUMENTS.
If the user provides files (org charts, project briefs, team rosters), read them first. If they describe the product or initiative, use that context to infer likely stakeholders.
Instructions
-
Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
-
Classify each stakeholder on two dimensions:
- Power (High/Low): Their ability to influence decisions, resources, or outcomes
- Interest (High/Low): How much the project directly affects them or how engaged they are
-
Place stakeholders in the Power × Interest grid:
| | High Interest | Low Interest | |---|---|---| | High Power | Manage Closely — Regular 1:1s, involve in decisions, seek their input early | Keep Satisfied — Periodic updates, escalate only critical issues | | Low Power | Keep Informed — Regular status updates, invite to demos, gather feedback | Monitor — Light-touch updates, available on request |
-
For each quadrant, recommend:
- Communication frequency (daily, weekly, bi-weekly, monthly)
- Communication format (1:1, email, Slack, meeting, dashboard)
- Key messages and framing
- Potential risks if this stakeholder is neglected
-
Create a communication plan table:
| Stakeholder | Role | Power | Interest | Strategy | Frequency | Channel | Key Message | |---|---|---|---|---|---|---|---|
-
Flag potential conflicts: Identify stakeholders with competing interests and suggest alignment strategies.
Think step by step. Save the stakeholder map as a markdown document.
Further Reading
- The Product Management Frameworks Compendium + Templates
- Team Topologies: A Handbook to Set and Scale Product Teams
Related Skills
MaVoid-Team/wwas
development
VerifiedTrustedCommunity
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/user-stories
content-media
VerifiedTrustedCommunity
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/test-scenarios
testing
VerifiedTrustedCommunity
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/summarize-meeting
testing
VerifiedTrustedCommunity
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
SKILL.mdUpdated Apr 16, 2026