Mmcp.market

negotiation skill

by wondelai·wondelai/skills·2.3k stars·MIT

Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", "anchoring", "how do I ask for a raise", "get a better deal", or "they wont budge on price". Also trigger when preparing for a vendor negotiation, resolving a pricing dispute, or navigating a high-stakes conversation where both sides need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product and marketing, see influence-psychology.

A100/100content scan

Is the negotiation skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the negotiation skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/product-strategy/skills/negotiation ~/.claude/skills/negotiation
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Negotiation

Tactical empathy-based negotiation framework from FBI hostage negotiator Chris Voss. Understand the emotional drivers behind decisions and use proven techniques to build rapport, uncover hidden information, and reach better outcomes.

Core Principle

People want to be understood and feel safe. The most effective path to "yes" runs through empathy, active listening, and emotional intelligence -- not logic, arguments, or compromise. Treat every negotiation as a discovery process: your assumptions are hypotheses to test, and the other side's needs (respect, security, autonomy) matter more than their stated positions. Never split the difference -- no deal is better than a bad deal.

Scoring

Goal: 10/10. Score 1 point per satisfied Quick Diagnostic row (6 rows), plus up to 4 points for execution quality: emotions labeled out loud (+1), "That's right" earned not "You're right" (+1), no "Why?" / no splitting the difference / no chasing "yes" (+1), at least one Black Swan surfaced (+1). Bands: 9-10 = audit delivered, calibrated questions and BATNA prepared, "That's right" achieved, Black Swans hunted; 5-6 = some prep but arguing the position or chasing "yes"; <=3 = no audit, no BATNA, splitting the difference. Always state the current score and the specific gaps to reach 10/10.

Framework

1. Tactical Empathy

Core concept: Consciously imagine yourself in the counterpart's situation, then vocalize their perspective to create trust and openness.

Why it works: When people feel understood, brain chemistry shifts toward trust and cooperation, short-circuiting defensive reactions. Empathy is not agreement -- you can understand their position while advocating your own.

Key insights:

  • Before responding, ask: "What is their world like right now?"
  • Articulate their situation, pressures, and fears before stating your position
  • Empathy must be genuine, not performed -- people detect fakeness instantly
  • Unconditional positive regard: respect them as a person regardless of disagreement
  • Emotions are contagious -- stay calm and positive; slow pace enables clear thinking

Product applications:

Copy patterns:

  • "I understand you're dealing with..."
  • "It seems like this is creating pressure for your team..."
  • "Before we talk about next steps, I want to make sure I understand where you're coming from..."

See references/techniques.md for the full 21-technique reference -- each section below points to the part you need at the moment you need it. Open it now for The Power of Apology and Pause, which has no section here.

2. Mirroring

Core concept: Repeat the last 1-3 critical words your counterpart said, with a curious, upward-inflecting tone, then go silent.

Why it works: Mirroring signals deep listening, creating familiarity and rapport. It prompts elaboration without direct questions, revealing more than the counterpart intended to share.

Key insights:

  • Repeat the key or emotion-laden words back as a gentle question
  • Wait silently (4+ seconds) for them to expand
  • Works in person, on the phone, and in written communication
  • The simplest technique, but often the most effective for information gathering

Product applications:

Copy patterns:

  • "[Key phrase they used]?" (with question mark)
  • "You mentioned [their exact words]..."
  • "When you say [mirror], what does that look like?"

3. Labeling

Core concept: Identify and verbalize the counterpart's emotions or perspective using neutral phrases: "It seems like...", "It sounds like...", "It looks like..."

Why it works: Naming emotions validates them -- labeling negative emotions diffuses their power, labeling positive emotions reinforces them. The tentative phrasing gives room to correct you, which deepens the conversation either way.

Key insights:

  • Always use third-person phrasing ("It seems like..."), never "I think you..."
  • After labeling, be silent -- let them respond
  • A wrong label still pays: their correction is valuable information
  • Watch for emotional shifts that signal you've hit the mark

Product applications:

Copy patterns:

  • "It seems like..."
  • "It sounds like you're feeling..."
  • "If I'm reading this right, it feels like..."

4. Calibrated Questions

Core concept: Open-ended "How...?" and "What...?" questions that shape the conversation while giving the counterpart the illusion of control.

Why it works: Calibrated questions engage the counterpart's problem-solving mind, making them feel in charge while you steer. They force the other side to consider your position without you stating it, and avoid the defensiveness "Why?" creates.

Key insights:

  • Start with "How" or "What" -- avoid "Why" (sounds accusatory)
  • "How am I supposed to do that?" is the most powerful pushback without saying no
  • Keep the tone genuinely collaborative, never sarcastic
  • Exception for "Why": only when you want them to defend something favorable to you ("Why would you ever choose our company?")
  • Follow every "yes" with "How...?" to secure implementation commitment

Product applications:

Copy patterns:

  • "How am I supposed to do that?"
  • "What's the biggest challenge you're facing?"
  • "What would it take to make this happen?"

For No-oriented questions ("Would it be unreasonable to...?") and tactical mislabeling to draw out a corrective "No", see techniques.md section 8 when a counterpart is guarded or stalling.

5. Accusation Audit

Core concept: Before negotiating, list and preemptively verbalize every negative thing the counterpart might think or say about you.

Why it works: Naming fears and criticisms before the other side does removes their power -- it often triggers reassurance ("Oh, I don't think that...") and at minimum neutralizes objections. Addressing the elephants first demonstrates self-awareness and builds trust.

Key insights:

  • Brainstorm every negative they might think before the meeting
  • Deliver the audit early in the conversation, not after objections surface
  • Overshoot on purpose -- the list should sound slightly worse than what they actually think
  • Particularly powerful when you're the party with less leverage

Product applications:

Copy patterns:

  • "You probably think..."
  • "I know this might seem like..."
  • "You might be wondering why you should even listen to..."

6. "That's Right"

Core concept: Summarize the counterpart's position -- facts, emotions, and concerns -- so accurately that they respond with "That's right." This is the breakthrough moment in any negotiation.

Why it works: "That's right" signals the person feels completely understood, shifting their mindset from adversarial to collaborative. It is fundamentally different from "You're right," which usually means they're dismissing you.

Key insights:

  • "That's right" is the two most powerful words in negotiation; if you get "You're right," keep working -- you haven't connected yet
  • Include emotional subtext in your summary, not just facts
  • Let them say "No" first to feel safe, then work toward "That's right"
  • Use the Rule of Three: confirm agreement three times in three different ways

Product applications:

Copy patterns:

  • "Let me make sure I understand..."
  • "If I'm hearing you correctly..."
  • "It sounds like [complete summary of their position including emotions]..."

For the three types of Yes (counterfeit, confirmation, commitment) and the Rule of Three confirmation sequence, see techniques.md sections 10-11 when closing or locking in a commitment.

7. Ackerman Bargaining

Core concept: A systematic monetary negotiation method: calculated offers in decreasing increments (65% -> 85% -> 95% -> 100% of target) with precise non-round numbers and a non-monetary bonus at the end.

More skills from wondelai/skills

  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • A37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Ablue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
  • Aclean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

All agent skills → · MCP servers