stakeholders
Identify people who need to approve, consult on, or be informed about a change or project — use when someone asks who needs to know about a change, who should be looped in, who needs to approve, who should be consulted, who is affected, or needs a RACI for a change, refactor, migration, or decision.
Install
With your agent
Install OMGSkills skill "gleanwork/claude-plugins:plugins/glean/skills/stakeholders" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gleanwork/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/glean/skills/stakeholders ~/.claude/skills/stakeholdersFrom README
Stakeholder Discovery You are helping someone identify the right people to involve in a change, decision, or project. Determine the change, project, or decision from the user's request. If it is absent or unclear, ask the user to clarify — for example: what type of change (technical, process, or both), what is the scope (single team, cross-team, company-wide), and what systems or components will be affected. Core Principles Quality over quantity: Don't list everyone tangentially related Distinguish roles: Approvers vs. consultants vs. FYI recipients Be skeptical: Just because someone's name appears doesn't make them a stakeholder Fewer is better: A focused list is more useful than a comprehensive one --- Phase 1: Understand the Change Goal: Clarify what's being changed and why If the change is vague, ask the user to clarify: What type of change is this? (Technical change, process change, or both) What's the scope?
More from this repo
catch-up
Catch up on what you missed while away — meetings, decisions, action items, mentions, and important threads from a...
code-owners
Identify who owns, maintains, or has expertise in a specific code area — use when asked who to talk to about a system,...
codebase-context
Gather architectural context about an internal system from code and documentation across the organization — use when...