# Stakeholder Identification

Map every stakeholder before engaging anyone.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill stakeholder-identification -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Map every stakeholder before engaging anyone. Use when launching an initiative, scoping discovery, or building an engagement plan from scratch.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Stakeholder Identification

## Purpose

Map every stakeholder before engaging anyone. This skill produces a comprehensive, equity-aware stakeholder set, not just the obvious sponsors and users, but the gatekeepers, the impacted communities, and the voices your team defaults to overlooking.

Most PM stakeholder lists are written from memory in five minutes. They reliably capture executives, product peers, and the most vocal users. They reliably miss the marginalized user groups who bear the product's consequences without having the organizational power to shape its decisions. This skill forces a slower, more structured brainstorm that builds the foundation for every engagement decision that follows.

Use this before stakeholder-mapping (which prioritizes) and before stakeholder-engagement-advisor (which plans per-stakeholder outreach). Identification comes first, you cannot prioritize people you haven't named.

## Input

**Works best with:** The initiative, product, or decision you're mapping stakeholders for.
**Also useful:** Stakeholders already on your list (the skill's job is to find who's missing), org context, and affected communities.

Anything supplied with the invocation itself, text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line, counts as answers already given. Use it and skip whatever it covers; don't re-ask.

**Arriving empty-handed? That works too.** The skill asks what the initiative is and who it touches, then runs the equity-aware sweep.

**Example invocation:** `Identify stakeholders for migrating all customers to the new billing system by Q4.`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/stakeholder-identification/SKILL.md