Skill Market

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.

GitHub
githubcommunityagent-skill-repositoryagent-skillsagentic-skillsclaude-code-marketplaceclaude-code-pluginsclaude-cowork-plugin
0.0
0 installs26.6K GitHub starsby phuryn

Skill Introduction

Overview
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.

Core value

Turns reusable Other know-how into an installable skill, helping users complete github, community, agent-skill-repository, agent-skills work faster.

Target users

  • Developers, testers, and maintainers who handle Other tasks in Focus Code.
  • Teams that already trust workflows or content from phuryn.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, agent-skill-repository, agent-skills that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Other, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, agent-skill-repository, agent-skills, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install stakeholder-map-fbd2f4
View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

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

  1. Identify stakeholders: List all relevant individuals and groups — executives, engineering leads, designers, marketing, sales, support, legal, finance, external partners, and end users.

  2. 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

  3. 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

  4. 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

  5. Create a communication plan table:

    StakeholderRolePowerInterestStrategyFrequencyChannelKey Message

  6. 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

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet