influence

Plan stakeholder alignment and script persuasion conversations for engineering manager requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill influence-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: influence
Source: https://github.com/imsus/cto/tree/main/.agents/skills/influence
Command: npx skills add https://github.com/imsus/cto --skill influence-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps engineering managers persuade stakeholders, neutralize resistance, and secure approvals or resources when they lack direct authority.

Core Features & Use Cases

  • Tactical influence methods: Nemawashi for pre-aligning stakeholders, Decoy Pricing for structured asks (including headcount), Reverse Psychology for pull-based hiring conversations, and LMDTFY for upward delegation and trust-building.
  • Resistance-handling conversation techniques: Label the Concern to disarm objections early, and Get to "That's Right" to achieve genuine agreement through precise reflection.
  • Headcount and positioning frameworks: A layered approach to arguing for headcount (alignment on problem → approach → team execution → then people) and a 3-level model for visibility/trust (Known → Appreciated → Trusted).
  • Practical politics and relationship modes: Politics as a neutral skill, plus Giver / Matcher / Taker guidance to choose the right collaboration posture.
  • Use Case: Prepare a headcount request that has a stakeholder-specific message, anticipates objections, and lands on the right decision layer with a clear plan and risks.

Quick Start

Ask the influence skill to build a stakeholder plan and a ready-to-send script for your upcoming buy-in conversation.

Frequently Asked Questions about influence

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

FAQPage Schema
How do I get stakeholder buy-in for engineering headcount requests without direct authority?

To secure stakeholder agreement for headcount requests without direct authority, use a layered persuasion framework that aligns on the problem, approach, and execution before arguing for people. This method maps stakeholder-specific messages and anticipates executive objections.

What is the best way to pre-align executives before a cross-team engineering decision?

Pre-aligning executives before cross-team engineering decisions is best achieved using Nemawashi, a tactical influence method for stakeholder mapping and neutralizing resistance. This structured approach secures approvals before the formal conversation occurs.

How do I handle resistance and disarm objections during engineering leadership conversations?

Handling resistance in engineering leadership conversations requires techniques like Label the Concern to disarm objections early and Get to "That's Right" to achieve genuine agreement. These conversation scripts help neutralize pushback from peers and managers.

When should I use structured persuasion tactics for organizational politics in engineering management?

Structured persuasion tactics for organizational politics should be used during calibration outcomes, hiring conversations, and cross-team alignment. They apply whenever an engineering manager needs to navigate political risk and secure resources without formal authority.

Can I use negotiation frameworks to improve visibility and trust with engineering stakeholders?

Yes, you can use negotiation frameworks to improve visibility and trust with engineering stakeholders by applying a 3-level model: Known, Appreciated, and Trusted. This positions headcount asks and collaboration postures effectively using Giver, Matcher, or Taker modes.

What is the step by step approach to prepare a stakeholder plan for an engineering approval?

Preparing a stakeholder plan for engineering approval involves decision targeting, stakeholder mapping, method selection, and messaging. It generates a ready-to-send script that anticipates objections and lands on the right decision layer with clear risks.