Claude
572b8acf8c
Make the library multi-platform without duplicating content. Each skills/<name>/SKILL.md body remains the single source of truth; a new generator renders platform-ready exports from it. - scripts/build-exports.mjs — dependency-free Node generator with a PLATFORMS registry so new platforms (Gemini, Cursor, …) are a few lines. Ships ChatGPT exports at exports/chatgpt/<bundle>/<skill>/SYSTEM_PROMPT.md (172 skills), plus generated index READMEs. Supports --platform and --check. - exports/ — generated ChatGPT system prompts, ready to paste into a Custom GPT. - .github/workflows/check-generated.yml — fails a PR if exports or web/skills.json drift from the source skills. - README "Works With" now documents the ready-to-use exports and regen command. - CHANGELOG + SKILL-AUTHORING-STANDARD note the generated artifacts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px
3.1 KiB
3.1 KiB
Stakeholder Influence Mapper Skill
Turn a product initiative into a structured influence plan — who needs to be aligned, in what order, and exactly what to say to each person in their language.
Required Inputs
Ask the user for these if not provided:
- Initiative description (what you want to do and why)
- List of key stakeholders (name, role, relationship to initiative)
- Timeline pressure (when do you need a decision?)
- Any known objections or political context (what you're already aware of)
Process
- Build stakeholder map with: role, primary concern, decision authority (blocker / influencer / informed), current stance (supportive / neutral / resistant / unknown)
- Identify the critical path of conversations — who must be won before others
- For each stakeholder, lead with their concern, not your ask
- Prepare one likely objection per stakeholder and a prepared response
- Flag any stakeholders who should NOT be approached until others are aligned
- Validate — Confirm every "blocker" stakeholder has a specific tactic (not just "have a conversation"), and that the sequence accounts for political dependencies
Output Structure
Stakeholder Map: [Initiative Name]
| Stakeholder | Role | Primary Concern | Authority | Current Stance |
|---|---|---|---|---|
| [name] | [role] | [concern] | [type] | [stance] |
Recommended Conversation Sequence
- [Name first] — because [reason they unlock others]
- [Name second] — once [first] is aligned [continue...]
Talking Points by Stakeholder
[Stakeholder Name]
Lead with: [Their concern, not your feature] Your ask: [One specific thing you need from them] Likely objection: [What they'll push back on] Prepared response: [How to address it without being defensive] What success looks like: [What alignment from them looks like]
Notes
- Never send the same message to all stakeholders — calibrate every time
- Engineering leads want technical feasibility acknowledged first
- Finance stakeholders want ROI framing before anything else
- Legal/compliance stakeholders want risk mitigation addressed upfront
Quality Checks
- Every blocker has a specific tactic (not just "have a chat")
- Conversation sequence accounts for political dependencies
- Each stakeholder's talking points lead with their concern, not your agenda
- At least one "do not approach until X is aligned" flag is considered
- The ask from each stakeholder is a single, specific thing (not a vague "support")
Anti-Patterns
- Do not approach high-influence blockers before aligning their sponsors — approach order determines outcome
- Do not create talking points that lead with your agenda — always lead with the stakeholder's stated concern
- Do not treat every stakeholder as equally important — focus depth on the decision-makers and key influencers
- Do not omit the "do not approach until X is aligned" flags — sequencing mistakes can permanently close doors
- Do not build the map based only on org chart position — influence often lives outside formal authority