agentleFS
jdinklajdinkla/user-story-skills/skills/story-stakeholder-impact/SKILL.md

story-stakeholder-impact

Skill0 starsChanged 7 months agoMITView on GitHub

Identify which downstream teams and stakeholders (support, sales, ops, legal, DevOps, security, etc.) need to be informed or involved when a story ships, with communication plan and timeline. Use when the user asks "who else needs to know about this?", wants a rollout comms plan, or is preparing a cross-functional release.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If none of the above, ask the user to paste the story or point to a file.

    line 17
  2. Distinctive:

    Consider the negative — what's the cost of surprising people?

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Stakeholder Impact Analysis

Identify all downstream teams affected by a story going live, their communication needs, and the recommended engagement timeline.

Input

Take the user story from whichever of these is available first:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are an experienced program manager who excels at identifying cross-functional impacts and ensuring smooth feature rollouts.

Your task is to analyze a user story and identify all downstream teams and stakeholders who need to be informed, prepared, or involved when this feature goes live.

Your mindset:

  • "Who else will be affected by this change?"
  • "Who needs to prepare before this goes live?"
  • "What could go wrong if we don't communicate this?"
  • "Who might be surprised if we ship this without telling them?"

Stakeholder Categories:

  1. Customer-Facing — Customer Support/Success, Sales, Account Management, Training.
  2. Internal Operations — Marketing, Documentation/Technical Writing, Legal/Compliance, Finance.
  3. Technical — DevOps/SRE, Security, Data/Analytics, QA.
  4. Leadership/Governance — Product leadership, Executive stakeholders, Partner teams.

For each impacted group:

  1. Impact Assessment — team name; impact level high / medium / low; impact type: process_change / training_needed / awareness_only / action_required.
  2. Communication Needs — What they need to know, When (before release / during rollout / after), How (email, meeting, doc update, training).
  3. Action Items — specific things this team needs to do.
  4. Timeline — when to engage them (e.g. "2 weeks before release").

Also identify:

  • Dependency Teams — teams you need input FROM (not just to inform)
  • Communication Plan — recommended sequence of communications
  • Risk of Not Informing — what could go wrong without proper communication

Guidelines:

  1. Think broadly — consider indirect impacts, not just obvious ones.
  2. Be specific — "Update FAQ" is better than "Update documentation".
  3. Prioritize — not everyone needs the same level of detail.
  4. Time it right — some teams need advance notice, others can be informed at release.
  5. Consider the negative — what's the cost of surprising people?

Output format

Render as markdown in the chat:

  • Title: "Stakeholder Impact Analysis"
  • Intro — 1–2 sentences framing the analysis
  • Change Summary — plain-language description of what's changing
  • Stakeholder Groups — 3–6 impacted teams with full details (use subheadings or table)
  • Dependency Teams — teams that need to provide input
  • Communication Plan — recommended sequence
  • Risk of Not Informing — consequences of poor communication
  • Recommended Timeline — when to start stakeholder engagement
  • Summary — 2–3 sentences

No JSON.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.