stakeholder-surprise-detector

Name: stakeholder-surprise-detector
Availability: InStock
Author: aurora-atoms

Identify accountable roles likely surprised by bounded changes from structured inputs.

Updated Jun 1, 2026

Search Tags:#governance #risk management #alignment #stakeholder #change management #project delivery

Ready to run

npx skills add https://github.com/aurora-atoms/lattice --skill stakeholder-surprise-detector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stakeholder-surprise-detector
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/stakeholder-surprise-detector
Command: npx skills add https://github.com/aurora-atoms/lattice --skill stakeholder-surprise-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents project delays and friction by identifying accountable roles that are likely to be materially surprised by a change, ensuring they are engaged at the right time without triggering unnecessary consensus-seeking.

Core Features & Use Cases

Impact Mapping: Analyzes bounded changes against dependencies, operations, and commitments to identify affected roles.
Engagement Planning: Generates minimal, evidence-based briefing materials to ensure feedback is obtained while it is still cost-effective.
Use Case: Use this when planning a system migration or policy update to ensure that cross-team dependencies and compliance requirements are addressed early, preventing late-stage objections.

Quick Start

Use the stakeholder-surprise-detector skill to analyze the proposed API deprecation plan and generate an engagement strategy for all affected internal teams.

Frequently Asked Questions about stakeholder-surprise-detector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify stakeholders likely to be surprised by a system migration?▼

Stakeholder surprise detection involves analyzing bounded changes against cross-team dependencies and historical evidence to pinpoint materially affected roles. This mechanism prevents late-stage objections by generating a minimal, evidence-based engagement plan before changes are finalized.

How do I create an engagement plan for architectural changes affecting cross-team dependencies?▼

To create an engagement plan for architectural changes, you must input change boundaries, affected systems, and historical evidence. The output is a minimal, evidence-based briefing strategy that ensures feedback is obtained while it remains cost-effective.

Can I use stakeholder surprise detection for policy rollouts and compliance updates?▼

Yes, you can use stakeholder surprise detection for policy rollouts and compliance updates. It identifies accountable roles impacted by the bounded change and generates targeted engagement materials to ensure compliance requirements are addressed early.

What is the best way to prevent late-stage objections during project delivery?▼

The best way to prevent late-stage objections during project delivery is to identify and engage accountable roles before surprises occur. This approach generates minimal briefing materials to gather feedback while it is still cost-effective, avoiding unnecessary consensus-seeking.

What inputs do I need to generate a stakeholder engagement strategy for an API deprecation?▼

To generate a stakeholder engagement strategy for an API deprecation, you need structured input detailing change boundaries, affected systems, and historical evidence. This data identifies materially surprised roles and produces a minimal engagement plan.

When should I avoid using stakeholder surprise detection for change management?▼

You should avoid using stakeholder surprise detection for change management when your project lacks defined change boundaries or historical evidence. Without structured input of affected systems and dependencies, the tool cannot accurately identify materially impacted roles.