Skip to content
cccskills
FreePublished on GitHub

power-map

Map stakeholders by power and interest to plan engagement strategy. Use when starting multi-stakeholder initiatives.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • agents/openai.yaml189 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Stakeholder Power-Interest Map

Map stakeholders by power and interest to plan engagement strategy.

When to Use

When starting an initiative that involves multiple stakeholders.

The Framework

Power-Interest Grid

Low InterestHigh Interest
High PowerKeep SatisfiedManage Closely
Low PowerMonitorKeep Informed

Influence Pyramid

Beyond formal power, map informal influence:

  • Top tier: Decision makers, budget holders
  • Middle tier: Gatekeepers, team leads
  • Base tier: Super-connectors, exec assistants

The Process

1. List Stakeholders

Gather:

  • Names and roles
  • Organizational position
  • Known relationships
  • Allies and blockers

2. Map to Grid

Place each stakeholder in the 2x2 based on:

  • Power: Formal authority, budget control, veto ability
  • Interest: How much they care about this initiative

3. Build Influence Pyramid

Identify informal power:

  • Who controls access?
  • Who influences opinion?
  • Who connects people?

4. Profile High-Power Stakeholders

For each, document:

  • Goals and success metrics
  • Likely concerns (political, operational, reputational)
  • Preferred communication style
  • Political risks for you

5. Create Engagement Plan

For each high-power stakeholder:

  • Cadence and channel
  • Format and owner
  • Key message (tied to their priorities)
  • Quick win to offer
  • Fallback if they resist

Output

  • Power-Interest matrix with names
  • Influence pyramid with rationale
  • High-power profiles table
  • Engagement plan table
  • Top 3 political pitfalls to avoid

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

See all skills by itseffi

Report a problem with this skill