本文へ移動
cccskills
無料GitHub で公開

negotiation

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md18.5 KB
  • references/techniques.md16.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

ContextApplicationExample
Customer supportAcknowledge frustration before solving"I understand this outage is affecting your team's deadline"
Sales callsVoice the prospect's pressures"It sounds like you're under pressure to show results this quarter"
Pricing conversationsAcknowledge budget constraints upfront"I know adding another tool to the stack feels risky right now"

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:

ContextApplicationExample
Discovery callsMirror key concerns to get elaborationClient: "The timeline is tight." You: "The timeline is tight?"
User interviewsEncourage deeper explanation of painUser: "It's just frustrating." You: "Frustrating?"
Objection handlingReflect to find the root cause"Doesn't fit your budget?"

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:

ContextApplicationExample
Customer complaintsName the frustration before solving"It sounds like you feel let down by our response time"
Sales objectionsLabel the underlying concern"It seems like there's a concern about implementation risk"
Churn preventionIdentify the real reason for leaving"It sounds like something changed since you first signed up"

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:

ContextApplicationExample
Price negotiationPush back without refusing"How am I supposed to do that at that price point?"
Scope creepMake them own the constraint"What happens to the timeline if we add this?"
Stakeholder alignmentUncover hidden decision-makers"How does your team typically make decisions like this?"

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:

ContextApplicationExample
Price increase announcementPreempt anger before explaining"You're probably thinking we don't value your loyalty..."
Sales cold outreachAcknowledge the intrusion"I know you're busy and the last thing you want is another sales pitch..."
Service failure recoveryOwn the failure fully"You're probably furious, and you have every right to be..."

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:

ContextApplicationExample
Sales closingSummarize their needs before proposing"So your team needs X, you're worried about Y, and Z is the deal-breaker..."
Customer retentionShow you understand why they're leaving"Let me make sure I have this: the product isn't delivering on the promise we made..."
Negotiation closureConfirm understanding before terms"Let me make sure I understand: you need [X], by [date], and [constraint]..."

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.

Why it works: Decreasing increments signal you're approaching your limit, and precise numbers ($47,235 vs $47,000) feel calculated and final. The closing non-monetary gift signals generosity at the limit, making it psychologically harder to ask for more.

Key insights:

  • Set your target price first, then open at 65% and raise in decreasing increments: 85% -> 95% -> 100%
  • Use precise, non-round numbers on the final offer ($10,230 not $10,000)
  • Attach a non-monetary bonus to the final offer ("...and I'll include X")
  • Never make a concession without getting something in return

Product applications:

ContextApplicationExample
Salary negotiationStructure counter-offers systematicallyTarget $120K: open at $78K, move to $102K, $114K, final $120,350 + extra PTO
Vendor pricingMethodical price reductionTarget $50K: start $32.5K, move to $42.5K, $47.5K, final $49,850 + extended payment terms
SaaS enterprise dealsMulti-year pricing negotiationsDecreasing discount increments across contract years

Copy patterns:

  • "Based on our analysis, we can offer $[precise number]..."
  • "We've stretched as far as we can -- $[precise number], and we'll include [non-monetary bonus]"
  • "I've gone back to my team and the absolute best we can do is $[precise number]"

For setting the opening anchor, soft range-anchoring, and framing loss aversion, see techniques.md section 14 before you name the first number.

8. Black Swans

Core concept: Hidden, game-changing pieces of information that transform a negotiation once discovered. Every negotiation has approximately three lurking.

Why it works: Negotiations stall or fail when critical information stays hidden. Black Swans -- the unknown unknowns -- explain seemingly irrational behavior, and discovering even one can turn a stalemate into a breakthrough.

Key insights:

  • Three types: secret constraints (boss capped the budget), hidden motivations (this deal saves their job), unknown context (a competitor just moved)
  • Watch for anomalies -- odd reactions, hesitations, inconsistencies -- and listen in unguarded moments before and after meetings
  • If they seem irrational, diagnose: ill-informed, constrained, or hiding something?
  • Use all three leverage types -- positive (what they want), negative (what they fear), normative (their own stated values) -- to surface hidden information

Product applications:

ContextApplicationExample
Enterprise salesDiscover hidden budget or timeline constraints"What happens internally if this doesn't get resolved by Q3?"
Churn analysisUncover the real cancellation reason"It seems like something changed -- what happened?"
Hiring negotiationsDiscover the candidate's true priorities"What would make you regret not taking this offer?"

Copy patterns:

  • "What's the biggest thing I'm missing here?"
  • "Help me understand -- what's really driving this?"
  • "What would change everything about this situation?"

For applying the three leverage types, reading pronoun shifts that reveal who really decides, and using dynamic silence to draw out hidden information, see techniques.md sections 16, 20, and 21 when a negotiation stalls or you suspect a hidden decision-maker.

Handling Common Situations

  • They say "That's not fair": Stop immediately: "I want to be fair. Have I done something unfair? Let's discuss it."
  • They anchor with an extreme number: Don't counter; ask "How did you arrive at that figure?"
  • They stop responding: Send "Have you given up on [the project]?" -- triggers a "No" response
  • They seem irrational: Diagnose with calibrated questions: ill-informed, constrained, or hiding something?

Counterpart Styles

StyleSignsAdapt by...
AnalystMethodical, data-driven, hates surprisesUse facts, be patient, don't rush
AccommodatorFriendly, relationship-focused, avoids conflictBuild rapport, but pin down specifics
AssertiveDirect, time-conscious, wants to winBe efficient, stand firm, acknowledge their points

Insight: Great negotiators borrow from all three styles as needed.

Voice and Delivery

  • Default voice: Positive, warm, light-hearted (with a smile)
  • Critical moments: Late-Night DJ Voice -- slow, calm, downward inflection
  • After key statements: Pause 4+ seconds (tactical silence)
  • Watch their nonverbals: 7% words, 38% tone, 55% body language

See techniques.md sections 4 and 19 when you need the full Late-Night DJ Voice mechanics and the cues to read in their body language.

Common Mistakes

MistakeWhy It FailsFix
Splitting the differenceLukewarm outcomes nobody is happy withHold firm; no deal is better than a bad deal
Pushing for "yes"Makes people defensive; produces counterfeit agreementPursue "That's right"; let them say "No" first
Arguing your positionTriggers resistance and shuts down listeningUse calibrated questions and labels to let them talk
Skipping the accusation auditUnaddressed objections fester and derail laterList every negative they might think; address early
Countering an extreme anchor immediatelyValidates their anchor as the starting pointMirror, label, ask "How did you arrive at that?"
Using "Why?"Sounds accusatory and triggers defensivenessReplace with "What" and "How" questions
Treating "You're right" as successIt means they want you to go awayKeep working toward "That's right"

Quick Diagnostic

QuestionIf NoAction
Have I prepared an accusation audit?Objections will blindside youList every negative they might think; address early
Do I have 3-5 calibrated questions ready?You'll default to arguingDraft "How" and "What" questions targeting their needs
Have I identified my BATNA?You'll accept a bad deal under pressureDefine your walk-away point before negotiating
Am I aiming for "That's right"?You'll chase counterfeit "yes"Summarize their position until they affirm genuinely
Have I considered their negotiation style?One-size-fits-all will misfireAssess if they're Analyst, Accommodator, or Assertive
Am I hunting for Black Swans?You'll miss game-changing informationStay curious; watch for anomalies; ask about the unexpected

Further Reading

Based on Chris Voss's experience as an FBI hostage negotiator:

About the Author

Chris Voss is a former FBI lead international kidnapping negotiator who worked over 150 hostage situations in a 24-year career, and the founder of the Black Swan Group, which trains businesses in tactical negotiation. He has taught at Harvard Law School, Georgetown, and MIT Sloan; Never Split the Difference is one of the most widely recommended business books in the world.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Build 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.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

Guided 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.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

Create 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.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

Structure 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.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.

日本語の概要は準備中です。原文の説明を表示しています。

wondelai/skills2,3932026年9月11日 更新

wondelai のスキルをすべて見る

このスキルの問題を報告する