stakeholder-alignment

Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use `design-negotiation` (designer-toolkit).

2,036
installs: 0 up / 0 down, score 0.00
votes: 3,024
repo stars
Updated: 2 months ago
In the catalog since: 1 Oct 2026
From: owl-listener/designer-skills

Get it through your agent npx skills add owl-listener/designer-skills@stakeholder-alignment

Skill instructions

Rendered from the published SKILL.md, 19 lines.

Stakeholder Alignment

You are an expert in navigating stakeholder landscapes and creating alignment around design decisions.

What You Do

You create artifacts helping teams align with stakeholders on roles, decisions, communication, and feedback.

Alignment Artifacts

Stakeholder Map — Identify all stakeholders, map influence vs interest, categorize roles
RACI Matrix — Responsible, Accountable, Consulted, Informed per decision
Decision Framework — What needs input, who decides, how to resolve disagreements
Communication Plan — Who/what/when, cadence, channels, feedback timelines
Feedback Protocol — Format, timing, prioritization, conflict handling

Common Challenges

Stakeholders designing solutions, conflicting priorities, late-stage scope changes, missing stakeholders.

Best Practices

Map stakeholders at kickoff
Establish decision rights before conflict
Communicate proactively
Document decisions and rationale
Revisit as projects evolve

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "stakeholder-alignment"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository owl-listener/designer-skills
Listing on skills.sh

From owl-listener/designer-skills via skills.sh

Related skills

stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
2,791 installs
stakeholder-alignment
Help users master the art of leading without formal authority by identifying stakeholder incentives, neutralizing conflict through connection, and using co-creation to build shared ownership.
2,068 installs
deal-champion-mapping
Builds an evidence-graded stakeholder map for one active deal from titles, call notes, email and meeting activity, and CRM contact roles, naming the likely champion, economic buyer, and blockers, each with a confidence level tied to observed behaviour rather than title. Covers B2B buying committees and high-consideration B2C households. Use whenever the user mentions a champion, economic buyer, power map, deal org chart, multi-threading, single-threaded risk, or "who actually decides", even without the word stakeholder. Do NOT use for qualification scoring (mbfinotti/sales-skills@meddpicc-scorecard) or scanning notes for general risk (mbfinotti/sales-skills@deal-red-flags).
23,614 installs
competitive-analysis
Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.
2,383 installs
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
1,663 installs

More from owl-listener/designer-skills

presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.
3,063 installs
typography-scale
Create a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).
2,552 installs
visual-hierarchy
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).
2,499 installs
illustration-style
Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use `icon-system` (design-systems).
2,492 installs
color-system
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).
2,458 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.