← ClaudeAtlas

stakeholder-mapslisted

Builds a political map, not an org chart, showing who can kill your launch, who champions it and what to say to each stakeholder, with a Power × Interest grid, conflict map and weekly Sprint Cards. Use when aligning stakeholders around a launch or GTM initiative.
stefanoskarakasis/Product-Marketing-Skills · ★ 13 · AI & Automation · score 86
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# Stakeholder-Maps — Skill ## How This Works Stakeholder maps built in a vacuum are a waste of time. This skill builds a map anchored to political reality: who has power, who's a hidden champion, who's a silent blocker, and what to do before you're in the room. The skill runs in 7 steps: **Step 0** — Load brain context (ICP, positioning, GTM motion) and guardrails from `/context/meta-patterns.md` if it exists (e.g., "product launches without Sales Manage Closely engagement fail 80% of the time" — an example pattern shape, not a claim this skill has already observed). **Step 1** — Intake: Initiative description, success definition, timeline, and current champions/blockers. **Step 2** — Inversion: Who could sink this from inside? (If you can't name them, the map is assumed, not validated.) **Step 3** — Classification: Place each stakeholder on Power × Interest grid; assign political role (Champion, Blocker, Frozen, Gatekeeper, Performer, Floating Voter). **Step 4** — Conflict mapping: Identify stakeholder conflicts; define second-order risks and resolution owners. **Step 5** — Silent blocker scan: Which functions/roles aren't in the room but should be? **Step 6** — Output: HTML widget (grid + comms plan + conflict map + confidence assessment) + markdown diagnostic + Sprint Cards. **Step 7** — Learning Close: log the session to `/context/skill-sessions.md`. --- ## Trigger - **When:** Building a political stakeholder map for an initiative — who can kill it, who cham