phuryn/pm-skills

stakeholder-map

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/phuryn/pm-skills --skill stakeholder-map

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

  1. Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.
  1. 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
  1. Place stakeholders in the Power × Interest grid:
High InterestLow Interest
High PowerManage Closely — Regular 1:1s, involve in decisions, seek their input earlyKeep Satisfied — Periodic updates, escalate only critical issues
Low PowerKeep Informed — Regular status updates, invite to demos, gather feedbackMonitor — Light-touch updates, available on request
  1. 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
  1. Create a communication plan table:
StakeholderRolePowerInterestStrategyFrequencyChannelKey Message
  1. 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

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
phuryn
Community

pricing-strategy

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.

Installationen
1
GitHub Stars
27.246
Aktualisiert
16. Okt.
phuryn
Community

product-name

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.

Installationen
1
GitHub Stars
27.246
Aktualisiert
16. Okt.
phuryn
Community

review-resume

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

Installationen
2
GitHub Stars
27.241
Aktualisiert
16. Okt.
phuryn
Community

create-prd

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Installationen
1
GitHub Stars
27.241
Aktualisiert
16. Okt.