High power · High interest
Manage Closely
Invite early input. Work through decisions together.
Stakeholder MapInformation
A practical atlas for project alignment
Know who
needs what.
Turn a project brief and stakeholder roster into a power-and-interest map, a communication plan, and practical alignment suggestions.
High power · Low interest
Keep Satisfied
Offer concise updates. Escalate material decisions.
Low power · High interest
Keep Informed
Explain the change. Make room for feedback.
Low power · Low interest
Monitor
Share milestones. Stay available when needed.
The four strategies above are the upstream Skill's working framework. Ratings are provisional judgments, not measures of personal value.
The exchange
Bring the project.
Provide the goal, affected people or groups, decision rights, constraints, and known disagreements. Authorized organization charts and team rosters can add context.
Clear facts improve the map. Unknown authority should be marked for confirmation.
Leave with a plan.
A Markdown document with a stakeholder inventory, the four-quadrant grid, and a communication table covering role, power, interest, strategy, frequency, channel, and key message.
Potential conflicts receive suggested alignment steps.
Useful when the work
crosses teams.
Prepare a launch
Separate decision makers from frequent users and set a sensible engagement cadence.
Coordinate a change
Understand who needs a decision, a walkthrough, a brief update, or an opportunity to respond.
Surface competing needs
Make a date-versus-readiness or cost-versus-scope disagreement discussable before it grows.
Keep the boundary clear
Do not use a project engagement map to infer character, measure employee performance, or disclose private information.
Simple input.
Assistant-led work.
This is an instruction-only Skill. Load SKILL.md into a Skill-capable assistant, or provide it as task instructions. Host-specific installation and invocation vary.
No additional service API key is required for supplied-material planning. A model-capable assistant is still required, and its subscription or usage fees may apply.
- Attached documents require file-reading capability.
- Saving the result requires file-write capability. Otherwise, request the Markdown response and save it yourself.
- There is no automatic email, calendar, Slack, CRM, or organization-directory connection.
- Suggested channels and meetings are recommendations. No message is sent or meeting scheduled.
What has been checked
A preparation agent followed the original instructions using a fictional room-booking pilot. The saved output covered 10 stakeholders, all four quadrants, a 10-row communication plan, and two supplied conflicts.
An ambiguous-role boundary case kept authority unknown and did not claim to send messages. Twelve local structural assertions passed across those artifacts.
Evidence boundary
This was a source-guided demonstration, not a native-client installation, external-integration test, independent quality benchmark, or evidence of real-world stakeholder agreement.
This was a source-guided demonstration, not a native-client installation, external-integration test, independent quality benchmark, or evidence of real-world stakeholder agreement.
Use with judgment.
Power and interest depend on context and can change. Confirm inferred stakeholders, authority, communication preferences, and review triggers with the project owner. Use only information you are authorized to process or share.
The Skill does not approve spending, make release decisions, or resolve conflicts on anyone's behalf. Its Markdown is a reviewable planning draft.
Open source. Attributed.
Original Skill by Pawel Huryn, distributed from phuryn/pm-skills under the MIT License. The original SKILL.md, copyright notice, and full license are retained.
Core instructions are preserved unchanged. Added usage and provenance documentation does not imply upstream endorsement. Optional further-reading links are retained; the workflow does not require those sites.