skills.rest
JaviMontano
JaviMontanoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stakeholder-mapping

Generates influence-interest matrices, RACI charts, and communication plans from project context.

Updated Jun 28, 2026
Search Tags:#requirements analysis#stakeholder analysis#project governance#communication plan#power interest grid#raci matrix
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill stakeholder-mapping-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-mapping
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/stakeholder-mapping
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill stakeholder-mapping-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Project teams often miss hidden decision makers, veto holders, and resistance patterns because the formal org chart does not reflect real power dynamics, leading to stalled approvals and failed initiatives. ## Core Features & Use Cases - Stakeholder Analysis Artifacts: Produces influence/interest matrices, power/interest grids, RACI matrices, stakeholder registries, and communication plans with evidence-tagged findings. - Hidden-Stakeholder Detection: Applies six surfacing techniques (snowball, decision-trail, veto-scan, budget-trail, informal-network, meeting-archaeology) to separate formal authority from actual power. - Resistance Classification: Categorizes stakeholders into archetypes (Skeptic, Blocker, Passive-resister, Saboteur, Mourner) with a specific engagement response per type. - Use Case: Before starting a platform migration, run the analysis to map who controls budget, who can veto, and who is consulted off-record, then receive a communication plan and a warning banner if assumptions exceed 30%. ## Quick Start Ask the assistant to run stakeholder mapping on your project to produce an influence-interest map, RACI matrix, and communication plan.

Frequently Asked Questions about stakeholder-mapping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a stakeholder map for a new project?▼

Provide the project context such as documents, conversations, and existing systems, then request a stakeholder mapping analysis. The workflow produces an influence-interest matrix, RACI chart, stakeholder registry, and communication plan with every finding tagged by evidence type.

How to find hidden decision makers beyond the org chart?▼

Use six surfacing techniques: snowball interviews, decision-trail analysis of past sign-offs, veto-scan for blockers, budget-trail for money control, informal-network mapping, and meeting-archaeology. These separate formal authority from actual power.

What is the difference between a RACI matrix and a power-interest grid?▼

A RACI matrix assigns Responsible, Accountable, Consulted, and Informed roles for tasks, while a power-interest grid positions stakeholders by influence and engagement level. This analysis produces both, plus a communication cadence per stakeholder group.

When should stakeholder mapping not be used?▼

Do not use it for implementation work such as writing code, choosing class structures, or creating deployment scripts. It is strictly an analysis-phase deliverable and keeps implementation details out of scope by design.

What happens if stakeholder analysis relies mostly on assumptions?▼

If more than 30 percent of findings are tagged as assumptions, the output includes a prominent warning banner. The analysis is then held for validation rather than treated as decision-ready evidence.

Related Skills

Explore More Product & Management Skills→
thompson0012thompson0012
28

design-context-scout

Identify missing design context before starting a design sprint.

Community
Intermediate
jasonmeansjasonmeans
2

todo-map-stakeholders

Map internal stakeholders and create an engagement plan for projects.

Community
Basic
patrickdeanbrownpatrickdeanbrown

software-product-manager

Translate stakeholder needs into actionable product specifications and PRDs.

Community
Basic
qa-amanqa-aman
19

requirements-elicitation

Facilitate structured stakeholder requirement elicitation across interviews, workshops, observation, and document analysis.

Community
Advanced