{"id":"96109397-903b-4856-bcb8-8b77893d18e8","entityType":"agent","slug":"clawhub-deciqai-batna-zopa","name":"BATNA & ZOPA","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-batna-zopa","canonicalPath":"/agent/clawhub-deciqai-batna-zopa","generatedAt":"2026-10-12T18:07:17.663Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":null},"description":"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Skill: BATNA & ZOPA Owner: deciqai Summary: Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:52:27.725Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json) v1.0.4 | 2026-07-14T06:44:01.889Z | auto - A","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 999 downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:batna-zopa","sourceUrl":"https://clawhub.ai/deciqai/batna-zopa","homepage":"https://clawhub.ai/deciqai/skills/batna-zopa","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/batna-zopa","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/batna-zopa","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":null},"stars":null,"forks":null,"downloads":999,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"999 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:08:48.663Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T20:08:48.736Z","lastCrawledAt":"2026-10-11T20:08:48.663Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T20:08:48.663Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T17:52:27.725Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json)","fileCount":7,"zipByteSize":13838},{"version":"1.0.4","createdAt":"2026-07-14T06:44:01.889Z","changelog":"- Added new real-world example: AI startup term sheet & compute negotiation (2024–2026) for current market context - Expanded \"When to Use\" section to flag FOMO and scarcity pressures now common in AI/cloud deals - Linked to new example in main flow and \"Method in Action\" for direct relevance - Updated project description to reflect the increase from 164 to 225 open-source thinking skills - Removed outdated file: skill-card.md","fileCount":7,"zipByteSize":13630},{"version":"1.0.3","createdAt":"2026-07-08T10:54:16.334Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":6,"zipByteSize":10062},{"version":"1.0.2","createdAt":"2026-07-08T00:38:45.968Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":6,"zipByteSize":10303},{"version":"1.0.1","createdAt":"2026-07-07T20:30:04.309Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":7409},{"version":"1.0.0","createdAt":"2026-06-26T05:17:59.313Z","changelog":"Initial publish","fileCount":5,"zipByteSize":7530}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:batna-zopa","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-12T18:07:17.660Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-batna-zopa/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":null},"readme":"Skill: BATNA & ZOPA\n\nOwner: deciqai\n\nSummary: Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T17:52:27.725Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json)\n\nv1.0.4 | 2026-07-14T06:44:01.889Z | auto\n\n- Added new real-world example: AI startup term sheet & compute negotiation (2024–2026) for current market context  \n- Expanded \"When to Use\" section to flag FOMO and scarcity pressures now common in AI/cloud deals  \n- Linked to new example in main flow and \"Method in Action\" for direct relevance  \n- Updated project description to reflect the increase from 164 to 225 open-source thinking skills  \n- Removed outdated file: skill-card.md\n\nv1.0.3 | 2026-07-08T10:54:16.334Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:38:45.968Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T20:30:04.309Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-26T05:17:59.313Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 7 files, 13838 bytes\n\nFiles: examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md (5711b), examples/camp-david-accords-sinai-1978.md (4934b), examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (1901b), skill-card.md (2597b), SKILL.md (6977b), _meta.json (129b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo. More: deciqai.com/c/batna-zopa\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with `anchoring`, `signaling-games`, `repeated-games-reputation`, and `prisoners-dilemma`.\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n- Raising in the 2024–2026 AI market (term sheets, SAFEs) or committing to a GPU-cloud / compute contract, where FOMO and \"capacity is scarce\" pressure obscure your real alternative\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary (`anchoring`). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) · [Camp David Accords, 1978](examples/camp-david-accords-sinai-1978.md)*\n*→ 2026 lens: [An AI startup's term sheet & compute contract (2024–2026)](examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md) — build your BATNA before you negotiate the raise.*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/batna-zopa** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/batna-zopa.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224347725\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n- Feld, B., & Mendelson, J. (2019). *Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist* (4th ed.). Wiley. Standard reference for term-sheet mechanics (liquidation preference, option pool, pro-rata, board control) that make up the multi-issue ZOPA in a fundraising negotiation — used in the 2024–2026 AI term-sheet example. (Round sizes and valuations vary by deal and period; not asserted as specific figures.)\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. https://www.pon.harvard.edu — the value-creation / multi-issue \"structural move\" applied when no single-issue (price-only) ZOPA exists, e.g. widening a valuation stalemate into a trade across preference, pool, and pro-rata.\n\nFile v1.0.5:examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md\n\n# Method in Action: An AI Startup's Term Sheet & Compute Contract (2024–2026)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe 2024–2026 AI funding market was bifurcated: a handful of \"hot\" AI startups fielded competing term sheets at rich valuations, while most founders negotiated from a weaker spot than the headlines suggested. BATNA/ZOPA cuts through the FOMO in both directions. This walks the five steps through a Series A raise, then a shorter compute-contract case — the two negotiations that most often decide an AI startup's fate. Figures are illustrative; the discipline is the point.\n\n### Case 1 — a Series A term sheet\n\n**Step 1 — Compute your BATNA.** A founder feeling flattered by one interested fund has no BATNA — \"they might pass\" is not an alternative. The real BATNA is concrete: *a second term sheet at $X*, or *18 months of runway at current burn that lets us raise later from a stronger revenue position*, each with a dollar value, timeline, and probability. The single highest-leverage move in the whole raise happens *before* any negotiation: run a **parallel process** so more than one fund is live at once, and extend runway so \"no deal now\" is survivable. A founder with 3 months of cash and one term sheet has, in effect, no BATNA — and the term sheet's terms will show it.\n\n**Step 2 — Set reservation & aspiration.** Reservation is the worst valuation/terms you'd still sign versus your BATNA — and terms are not just the number: liquidation preference, option-pool shuffle, board control, and pro-rata can swamp headline valuation. Aspiration is a defensible high anchor grounded in comparable 2024–2026 rounds, not a wish. Open above aspiration but justifiable.\n\n**Step 3 — Estimate their BATNA.** The VC's BATNA is *their next-best deal* plus the cost of missing a category winner. In a hot AI sub-sector, fund FOMO is real leverage *for the founder* — a fund that has already missed one breakout is negotiating against its own regret. Read behavior per the skill: a patient investor is signalling a strong BATNA (they have other deals); a fund pushing to sign before you can run your process is signalling a weak one (or is managing *your* BATNA down). Their reservation — the most dilution/price they'll accept — caps what you can get.\n\n**Step 4 — Find the ZOPA.** Overlap of the two reservation prices. If a fund's ceiling is below your floor, negotiating \"harder\" is wasted motion — make a **structural move** instead: add issues to trade (a smaller round at a better price + more pro-rata; a SAFE bridge to reach a metric that resets comps; a different lead). No ZOPA on valuation often has a ZOPA once you widen past the single number.\n\n**Step 5 — Distribute within the ZOPA.** Open at your favorable, defensible boundary (this composes with [anchoring](../anchoring/SKILL.md)). Concede in small steps; never \"split the difference\" reflexively. Trade variables — give on board observer seats to hold valuation, or accept a standard 1x non-participating preference to resist a larger option pool. Walk at your reservation, not before and not after. And run the falsifier: *what would tell me my read of their BATNA is wrong?* — e.g., they let your exploding-offer deadline lapse without blinking (their BATNA is stronger than you thought).\n\n> **Founder takeaway (startup):** Your term sheet is won before the negotiation, in the calendar. A live parallel process and an extra six months of runway *are* your BATNA; tactics can't manufacture leverage you didn't build. The founders who got clean 2024–2026 rounds weren't better talkers — they engineered a real alternative and were visibly willing to use it.\n\n### Case 2 — a compute / vendor commitment\n\nThe same five steps govern the other AI-era negotiation: committing to a GPU-cloud or inference contract.\n\n- **BATNA:** a second cloud's quote, spot/on-demand capacity, or a smaller commit with burst pricing — priced out, not gestured at.\n- **Reservation/aspiration:** the most you'd pay per unit given your BATNA; the discount you'd target given a multi-year commit.\n- **Their BATNA:** a provider with tight capacity has a strong BATNA (other buyers want the same H-class GPUs), which is *why* they push long lock-ins; a provider with idle capacity is weaker and will discount.\n- **ZOPA / structure:** if the headline rate won't move, trade terms — shorter commit, ramped volume, price step-downs, or portability clauses that lower your switching cost ([switching-costs](../switching-costs/SKILL.md)) — turning a no-ZOPA price fight into a multi-issue deal.\n\n> **Founder takeaway (SMB / capital-light):** Don't sign a long GPU or SaaS commit because a rep implies capacity is scarce and \"this price won't last\" — that pressure is a read on *your* BATNA. Get one competing quote before you negotiate; a single alternative quote is often worth more than any tactic, because it converts your reservation price from a feeling into a number.\n\n*Sources: Fisher, R., & Ury, W. (1981). Getting to Yes: Negotiating Agreement Without Giving In. Houghton Mifflin — the origin of BATNA and the \"develop your BATNA before you negotiate\" discipline applied here. Lax, D. A., & Sebenius, J. K. (1986). The Manager as Negotiator. Free Press — multi-issue value creation / structural moves when no single-issue ZOPA exists. Term-sheet mechanics (liquidation preference, option pool, pro-rata) per standard venture practice; see Feld, B., & Mendelson, J. (2019). Venture Deals (4th ed.), Wiley. Valuations, round sizes, and GPU pricing vary widely by deal and period and are not asserted here as specific figures — verify current comparables before relying on them.*\n\nFile v1.0.5:examples/camp-david-accords-sinai-1978.md\n\n# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of \"focus on interests, not positions\" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.\n\n**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:\n\n- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.\n- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.\n\nBoth BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.\n\n**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.\n\n**The structural move.** The mediating team did not \"negotiate harder.\" It unbundled positions into interests:\n\n- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.\n- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.\n\nThose interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.\n\n**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather than letting the parties trade positional concessions face to face, where every concession signals room for more. The output was two framework agreements signed September 17, 1978 (\"A Framework for Peace in the Middle East\" and \"A Framework for the Conclusion of a Peace Treaty between Egypt and Israel\"), followed by the Egypt–Israel Peace Treaty of March 26, 1979. Israel completed its withdrawal from the Sinai in 1982. Sadat and Begin shared the 1978 Nobel Peace Prize — and the treaty has held for over four decades.\n\nThe lesson the case burns in: when reservation prices don't overlap, the answer is a structural change to the negotiation itself — unbundle positions into interests, add issues, change the process — not more pressure inside a zone that doesn't exist.\n\nThe mapped steps:\n1. Compute your BATNA: both sides faced continued belligerency and war risk — specific, costly, and mutually understood fallbacks\n2. Set reservation & aspiration: Egypt — full sovereignty over all of the Sinai; Israel — a guaranteed security buffer; on the map-line framing, mutually exclusive\n3. Estimate their BATNA: the US mediation team assessed both sides' no-deal costs and used them to keep both delegations at the table for thirteen days\n4. Find the ZOPA: on positions, no ZOPA existed → structural move: reframe from positions to interests (sovereignty vs. security) and add issues (timelines, normalization, aid)\n5. Distribute within ZOPA: one-text procedure — a single mediator draft revised through repeated rounds until both sides could sign, avoiding concession-signaling\n\nPrimary source: Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Washington, DC: Brookings Institution. See also Fisher, R., & Ury, W. (1981/1991). *Getting to Yes*, on the Sinai interests example and the one-text procedure, and the official text of the Camp David Accords (September 17, 1978).\n\nFile v1.0.5:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nBATNA & ZOPA helps agents coach users through non-trivial negotiations by computing fallback options, reservation points, deal overlap, strategy, and falsifiers.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and agents use this skill to structure salary, term sheet, vendor, customer pricing, partnership, M&A, and similar transactional negotiations. It guides the user to identify BATNAs, estimate the counterparty's reservation point, test whether a ZOPA exists, and choose either deal tactics or a structural move.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill asks agents to add real-use negotiation failure patterns back into the skill file, which could expose sensitive deal details or personal information.\n\nMitigation: Do not update the skill file with real negotiation details unless the user explicitly consents and the content is redacted and reviewed by a human.\n\nRisk: Negotiation coaching can produce misleading recommendations if BATNA values, counterparty alternatives, or reservation points are guessed without evidence.\n\nMitigation: Require explicit assumptions, confidence checks, and a falsifier before using the analysis to decide whether to accept, counter, or walk away.\n\n## Reference(s):\n\n- [Sources - batna-zopa](references/sources.md)\n- [Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md)\n- [Camp David Accords - Egypt, Israel, and the Sinai (1978)](examples/camp-david-accords-sinai-1978.md)\n- [AI Startup Term Sheet and Compute Contract (2024-2026)](examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md)\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/)\n- [BATNA & ZOPA ClawHub page](https://clawhub.ai/deciqai/skills/batna-zopa)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown analysis with structured negotiation fields]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses hard-stop coaching prompts for novice users and a structured BATNA/ZOPA analysis for concrete deals.]\n\n## Skill Version(s):\n\n1.0.5 (source: release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 7 files, 13630 bytes\n\nFiles: examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md (5711b), examples/camp-david-accords-sinai-1978.md (4934b), examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (1901b), skill-card.md (2356b), SKILL.md (6846b), _meta.json (129b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo.\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with `anchoring`, `signaling-games`, `repeated-games-reputation`, and `prisoners-dilemma`.\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n- Raising in the 2024–2026 AI market (term sheets, SAFEs) or committing to a GPU-cloud / compute contract, where FOMO and \"capacity is scarce\" pressure obscure your real alternative\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary (`anchoring`). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) · [Camp David Accords, 1978](examples/camp-david-accords-sinai-1978.md)*\n*→ 2026 lens: [An AI startup's term sheet & compute contract (2024–2026)](examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md) — build your BATNA before you negotiate the raise.*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 225 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/batna-zopa** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1784011441889\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n- Feld, B., & Mendelson, J. (2019). *Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist* (4th ed.). Wiley. Standard reference for term-sheet mechanics (liquidation preference, option pool, pro-rata, board control) that make up the multi-issue ZOPA in a fundraising negotiation — used in the 2024–2026 AI term-sheet example. (Round sizes and valuations vary by deal and period; not asserted as specific figures.)\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. https://www.pon.harvard.edu — the value-creation / multi-issue \"structural move\" applied when no single-issue (price-only) ZOPA exists, e.g. widening a valuation stalemate into a trade across preference, pool, and pro-rata.\n\nFile v1.0.4:examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md\n\n# Method in Action: An AI Startup's Term Sheet & Compute Contract (2024–2026)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe 2024–2026 AI funding market was bifurcated: a handful of \"hot\" AI startups fielded competing term sheets at rich valuations, while most founders negotiated from a weaker spot than the headlines suggested. BATNA/ZOPA cuts through the FOMO in both directions. This walks the five steps through a Series A raise, then a shorter compute-contract case — the two negotiations that most often decide an AI startup's fate. Figures are illustrative; the discipline is the point.\n\n### Case 1 — a Series A term sheet\n\n**Step 1 — Compute your BATNA.** A founder feeling flattered by one interested fund has no BATNA — \"they might pass\" is not an alternative. The real BATNA is concrete: *a second term sheet at $X*, or *18 months of runway at current burn that lets us raise later from a stronger revenue position*, each with a dollar value, timeline, and probability. The single highest-leverage move in the whole raise happens *before* any negotiation: run a **parallel process** so more than one fund is live at once, and extend runway so \"no deal now\" is survivable. A founder with 3 months of cash and one term sheet has, in effect, no BATNA — and the term sheet's terms will show it.\n\n**Step 2 — Set reservation & aspiration.** Reservation is the worst valuation/terms you'd still sign versus your BATNA — and terms are not just the number: liquidation preference, option-pool shuffle, board control, and pro-rata can swamp headline valuation. Aspiration is a defensible high anchor grounded in comparable 2024–2026 rounds, not a wish. Open above aspiration but justifiable.\n\n**Step 3 — Estimate their BATNA.** The VC's BATNA is *their next-best deal* plus the cost of missing a category winner. In a hot AI sub-sector, fund FOMO is real leverage *for the founder* — a fund that has already missed one breakout is negotiating against its own regret. Read behavior per the skill: a patient investor is signalling a strong BATNA (they have other deals); a fund pushing to sign before you can run your process is signalling a weak one (or is managing *your* BATNA down). Their reservation — the most dilution/price they'll accept — caps what you can get.\n\n**Step 4 — Find the ZOPA.** Overlap of the two reservation prices. If a fund's ceiling is below your floor, negotiating \"harder\" is wasted motion — make a **structural move** instead: add issues to trade (a smaller round at a better price + more pro-rata; a SAFE bridge to reach a metric that resets comps; a different lead). No ZOPA on valuation often has a ZOPA once you widen past the single number.\n\n**Step 5 — Distribute within the ZOPA.** Open at your favorable, defensible boundary (this composes with [anchoring](../anchoring/SKILL.md)). Concede in small steps; never \"split the difference\" reflexively. Trade variables — give on board observer seats to hold valuation, or accept a standard 1x non-participating preference to resist a larger option pool. Walk at your reservation, not before and not after. And run the falsifier: *what would tell me my read of their BATNA is wrong?* — e.g., they let your exploding-offer deadline lapse without blinking (their BATNA is stronger than you thought).\n\n> **Founder takeaway (startup):** Your term sheet is won before the negotiation, in the calendar. A live parallel process and an extra six months of runway *are* your BATNA; tactics can't manufacture leverage you didn't build. The founders who got clean 2024–2026 rounds weren't better talkers — they engineered a real alternative and were visibly willing to use it.\n\n### Case 2 — a compute / vendor commitment\n\nThe same five steps govern the other AI-era negotiation: committing to a GPU-cloud or inference contract.\n\n- **BATNA:** a second cloud's quote, spot/on-demand capacity, or a smaller commit with burst pricing — priced out, not gestured at.\n- **Reservation/aspiration:** the most you'd pay per unit given your BATNA; the discount you'd target given a multi-year commit.\n- **Their BATNA:** a provider with tight capacity has a strong BATNA (other buyers want the same H-class GPUs), which is *why* they push long lock-ins; a provider with idle capacity is weaker and will discount.\n- **ZOPA / structure:** if the headline rate won't move, trade terms — shorter commit, ramped volume, price step-downs, or portability clauses that lower your switching cost ([switching-costs](../switching-costs/SKILL.md)) — turning a no-ZOPA price fight into a multi-issue deal.\n\n> **Founder takeaway (SMB / capital-light):** Don't sign a long GPU or SaaS commit because a rep implies capacity is scarce and \"this price won't last\" — that pressure is a read on *your* BATNA. Get one competing quote before you negotiate; a single alternative quote is often worth more than any tactic, because it converts your reservation price from a feeling into a number.\n\n*Sources: Fisher, R., & Ury, W. (1981). Getting to Yes: Negotiating Agreement Without Giving In. Houghton Mifflin — the origin of BATNA and the \"develop your BATNA before you negotiate\" discipline applied here. Lax, D. A., & Sebenius, J. K. (1986). The Manager as Negotiator. Free Press — multi-issue value creation / structural moves when no single-issue ZOPA exists. Term-sheet mechanics (liquidation preference, option pool, pro-rata) per standard venture practice; see Feld, B., & Mendelson, J. (2019). Venture Deals (4th ed.), Wiley. Valuations, round sizes, and GPU pricing vary widely by deal and period and are not asserted here as specific figures — verify current comparables before relying on them.*\n\nFile v1.0.4:examples/camp-david-accords-sinai-1978.md\n\n# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of \"focus on interests, not positions\" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.\n\n**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:\n\n- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.\n- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.\n\nBoth BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.\n\n**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.\n\n**The structural move.** The mediating team did not \"negotiate harder.\" It unbundled positions into interests:\n\n- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.\n- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.\n\nThose interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.\n\n**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather than letting the parties trade positional concessions face to face, where every concession signals room for more. The output was two framework agreements signed September 17, 1978 (\"A Framework for Peace in the Middle East\" and \"A Framework for the Conclusion of a Peace Treaty between Egypt and Israel\"), followed by the Egypt–Israel Peace Treaty of March 26, 1979. Israel completed its withdrawal from the Sinai in 1982. Sadat and Begin shared the 1978 Nobel Peace Prize — and the treaty has held for over four decades.\n\nThe lesson the case burns in: when reservation prices don't overlap, the answer is a structural change to the negotiation itself — unbundle positions into interests, add issues, change the process — not more pressure inside a zone that doesn't exist.\n\nThe mapped steps:\n1. Compute your BATNA: both sides faced continued belligerency and war risk — specific, costly, and mutually understood fallbacks\n2. Set reservation & aspiration: Egypt — full sovereignty over all of the Sinai; Israel — a guaranteed security buffer; on the map-line framing, mutually exclusive\n3. Estimate their BATNA: the US mediation team assessed both sides' no-deal costs and used them to keep both delegations at the table for thirteen days\n4. Find the ZOPA: on positions, no ZOPA existed → structural move: reframe from positions to interests (sovereignty vs. security) and add issues (timelines, normalization, aid)\n5. Distribute within ZOPA: one-text procedure — a single mediator draft revised through repeated rounds until both sides could sign, avoiding concession-signaling\n\nPrimary source: Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Washington, DC: Brookings Institution. See also Fisher, R., & Ury, W. (1981/1991). *Getting to Yes*, on the Sinai interests example and the one-text procedure, and the official text of the Camp David Accords (September 17, 1978).\n\nFile v1.0.4:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nGuides agents through BATNA and ZOPA analysis for non-trivial transactional negotiations, including term sheets, salary discussions, vendor contracts, customer pricing, partnerships, and M&A. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and business operators use this skill to model walk-away alternatives, reservation prices, counterpart alternatives, and the zone of possible agreement before making or accepting a deal. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Negotiation coaching may influence high-stakes business or financial decisions. <br>\nMitigation: Verify current market numbers and seek qualified legal or financial review before relying on the analysis. <br>\nRisk: Negotiation inputs may include sensitive deal facts. <br>\nMitigation: Avoid sharing confidential information beyond the agent environment and redact sensitive terms when possible. <br>\n\n\n## Reference(s): <br>\n- [Sources - batna-zopa](references/sources.md) <br>\n- [Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) <br>\n- [Camp David Accords - Sinai, 1978](examples/camp-david-accords-sinai-1978.md) <br>\n- [AI Startup Term Sheet and Compute Negotiation, 2024-2026](examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md) <br>\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/) <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/batna-zopa) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance] <br>\n**Output Format:** [Markdown] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Structured BATNA and ZOPA analysis with reservations, aspirations, opening offer, strategy, structural moves, and falsifier.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 6 files, 10062 bytes\n\nFiles: examples/camp-david-accords-sinai-1978.md (4934b), examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (1163b), skill-card.md (2192b), SKILL.md (6461b), _meta.json (129b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo.\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with `anchoring`, `signaling-games`, `repeated-games-reputation`, and `prisoners-dilemma`.\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary (`anchoring`). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) · [Camp David Accords, 1978](examples/camp-david-accords-sinai-1978.md)*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/batna-zopa** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508056334\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n\nFile v1.0.3:examples/camp-david-accords-sinai-1978.md\n\n# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of \"focus on interests, not positions\" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.\n\n**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:\n\n- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.\n- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.\n\nBoth BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.\n\n**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.\n\n**The structural move.** The mediating team did not \"negotiate harder.\" It unbundled positions into interests:\n\n- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.\n- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.\n\nThose interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.\n\n**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather than letting the parties trade positional concessions face to face, where every concession signals room for more. The output was two framework agreements signed September 17, 1978 (\"A Framework for Peace in the Middle East\" and \"A Framework for the Conclusion of a Peace Treaty between Egypt and Israel\"), followed by the Egypt–Israel Peace Treaty of March 26, 1979. Israel completed its withdrawal from the Sinai in 1982. Sadat and Begin shared the 1978 Nobel Peace Prize — and the treaty has held for over four decades.\n\nThe lesson the case burns in: when reservation prices don't overlap, the answer is a structural change to the negotiation itself — unbundle positions into interests, add issues, change the process — not more pressure inside a zone that doesn't exist.\n\nThe mapped steps:\n1. Compute your BATNA: both sides faced continued belligerency and war risk — specific, costly, and mutually understood fallbacks\n2. Set reservation & aspiration: Egypt — full sovereignty over all of the Sinai; Israel — a guaranteed security buffer; on the map-line framing, mutually exclusive\n3. Estimate their BATNA: the US mediation team assessed both sides' no-deal costs and used them to keep both delegations at the table for thirteen days\n4. Find the ZOPA: on positions, no ZOPA existed → structural move: reframe from positions to interests (sovereignty vs. security) and add issues (timelines, normalization, aid)\n5. Distribute within ZOPA: one-text procedure — a single mediator draft revised through repeated rounds until both sides could sign, avoiding concession-signaling\n\nPrimary source: Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Washington, DC: Brookings Institution. See also Fisher, R., & Ury, W. (1981/1991). *Getting to Yes*, on the Sinai interests example and the one-text procedure, and the official text of the Camp David Accords (September 17, 1978).\n\nFile v1.0.3:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nGuides agents through BATNA and ZOPA analysis for non-trivial negotiations, including walk-away points, reservation values, counterparty alternatives, and deal feasibility. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and business operators use this skill to structure salary, term-sheet, vendor, customer-pricing, partnership, and M&A negotiations. It helps identify each side's fallback, reservation point, likely agreement zone, and next negotiation move. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Negotiation outputs can depend on incomplete or overconfident estimates of fallback options, reservation values, and counterparty constraints. <br>\nMitigation: Use the skill's falsifier and verification checklist to document assumptions, pre-commit walk-away points, and seek qualified review for material legal, financial, employment, or M&A decisions. <br>\n\n\n## Reference(s): <br>\n- [Primary sources](references/sources.md) <br>\n- [Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) <br>\n- [Camp David Accords, 1978](examples/camp-david-accords-sinai-1978.md) <br>\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown analysis with structured fields and interactive coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user responses during novice coaching; no shell commands, API calls, or configuration output are produced.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 6 files, 10303 bytes\n\nFiles: examples/camp-david-accords-sinai-1978.md (4934b), examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (1163b), skill-card.md (2718b), SKILL.md (6561b), _meta.json (129b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo.\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with `anchoring`, `signaling-games`, `repeated-games-reputation`, and `prisoners-dilemma`.\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary (`anchoring`). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) · [Camp David Accords, 1978](examples/camp-david-accords-sinai-1978.md)*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/batna-zopa?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=batna-zopa** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783471125968\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n\nFile v1.0.2:examples/camp-david-accords-sinai-1978.md\n\n# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of \"focus on interests, not positions\" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.\n\n**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:\n\n- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.\n- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.\n\nBoth BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.\n\n**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.\n\n**The structural move.** The mediating team did not \"negotiate harder.\" It unbundled positions into interests:\n\n- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.\n- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.\n\nThose interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.\n\n**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather than letting the parties trade positional concessions face to face, where every concession signals room for more. The output was two framework agreements signed September 17, 1978 (\"A Framework for Peace in the Middle East\" and \"A Framework for the Conclusion of a Peace Treaty between Egypt and Israel\"), followed by the Egypt–Israel Peace Treaty of March 26, 1979. Israel completed its withdrawal from the Sinai in 1982. Sadat and Begin shared the 1978 Nobel Peace Prize — and the treaty has held for over four decades.\n\nThe lesson the case burns in: when reservation prices don't overlap, the answer is a structural change to the negotiation itself — unbundle positions into interests, add issues, change the process — not more pressure inside a zone that doesn't exist.\n\nThe mapped steps:\n1. Compute your BATNA: both sides faced continued belligerency and war risk — specific, costly, and mutually understood fallbacks\n2. Set reservation & aspiration: Egypt — full sovereignty over all of the Sinai; Israel — a guaranteed security buffer; on the map-line framing, mutually exclusive\n3. Estimate their BATNA: the US mediation team assessed both sides' no-deal costs and used them to keep both delegations at the table for thirteen days\n4. Find the ZOPA: on positions, no ZOPA existed → structural move: reframe from positions to interests (sovereignty vs. security) and add issues (timelines, normalization, aid)\n5. Distribute within ZOPA: one-text procedure — a single mediator draft revised through repeated rounds until both sides could sign, avoiding concession-signaling\n\nPrimary source: Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Washington, DC: Brookings Institution. See also Fisher, R., & Ury, W. (1981/1991). *Getting to Yes*, on the Sinai interests example and the one-text procedure, and the official text of the Camp David Accords (September 17, 1978).\n\nFile v1.0.2:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nHelps agents structure non-trivial negotiations by computing BATNA, reservation and aspiration points, estimating the other side's BATNA, checking the ZOPA, and choosing a walk-away strategy. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and agents use this skill to plan salary, term-sheet, vendor, customer-pricing, partnership, and M&A negotiations by modeling walk-away alternatives, deal ranges, and next negotiation moves. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Users may treat negotiation planning output as legal, financial, tax, HR, or M&A advice. <br>\nMitigation: Use the skill as decision support; for high-value contracts, employment packages, term sheets, or acquisitions, verify assumptions and involve qualified professionals before acting. <br>\nRisk: Incorrect BATNA, reservation-price, probability, or counterparty assumptions can produce misleading deal ranges or walk-away points. <br>\nMitigation: Validate the specific alternative, value, timeline, probability, and counterparty estimates before relying on the recommended strategy. <br>\nRisk: Direct BATNA discussion may be inappropriate in relationship-only disputes or cultures where explicit BATNA framing is taboo. <br>\nMitigation: Use the skill only for transactional negotiations where this framing fits, and adapt the conversation style to the relationship and cultural context. <br>\n\n\n## Reference(s): <br>\n- [Sources - batna-zopa](references/sources.md) <br>\n- [Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) <br>\n- [The Camp David Accords - Egypt, Israel, and the Sinai (1978)](examples/camp-david-accords-sinai-1978.md) <br>\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown analysis template with short questions and negotiation guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a BATNA/ZOPA worksheet with assumptions, strategy, and falsifier; may pause for user input in coach mode.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 7409 bytes\n\nFiles: examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (960b), skill-card.md (2260b), SKILL.md (6395b), _meta.json (129b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo.\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with [`anchoring`](../anchoring/SKILL.md), [`signaling-games`](../signaling-games/SKILL.md), [`repeated-games-reputation`](../repeated-games-reputation/SKILL.md), and [`prisoners-dilemma`](../prisoners-dilemma/SKILL.md).\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary ([`anchoring`](../anchoring/SKILL.md)). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md)*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783456204309\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n\nFile v1.0.1:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nHelps agents structure non-trivial transactional negotiations by computing BATNA, reservation points, aspirations, counterpart alternatives, and the ZOPA. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and employees use this skill to evaluate salary, term-sheet, vendor, partnership, M&A, customer-pricing, and other transactional negotiations. It guides agents to identify walk-away value, estimate the counterparty's alternatives, test whether a deal range exists, and choose a strategy. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Negotiation work can involve salary, business, vendor, or acquisition details that may be confidential. <br>\nMitigation: Avoid recording confidential specifics in persistent notes or skill edits unless the user is comfortable storing them. <br>\nRisk: A flawed BATNA, reservation point, or ZOPA estimate could lead to poor negotiation advice. <br>\nMitigation: Use the skill's verification checklist and falsifier step to test assumptions before acting on the strategy. <br>\n\n\n## Reference(s): <br>\n- [Sources - batna-zopa](references/sources.md) <br>\n- [Method in Action: Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) <br>\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/) <br>\n- [BATNA & ZOPA on ClawHub](https://clawhub.ai/deciqai/skills/batna-zopa) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance] <br>\n**Output Format:** [Markdown] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May include negotiation values, estimated ranges, strategy, structural moves, and falsifiers.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 7530 bytes\n\nFiles: examples/fisher-and-ury-1981-the-harvard-negotiation-project.md (3705b), references/sources.md (960b), skill-card.md (2564b), SKILL.md (6395b), _meta.json (129b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo.\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with [`anchoring`](../anchoring/SKILL.md), [`signaling-games`](../signaling-games/SKILL.md), [`repeated-games-reputation`](../repeated-games-reputation/SKILL.md), and [`prisoners-dilemma`](../prisoners-dilemma/SKILL.md).\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move (add issues, extend time, find new counterparty). Not \"negotiate harder.\"\n\n**Step 5 — Distribute within ZOPA:** Open at your favorable boundary ([`anchoring`](../anchoring/SKILL.md)). Make small concessions — don't split. Trade variables when single-issue stalls. Walk at reservation, not earlier or later.\n\n## Output: BATNA & ZOPA Analysis\n\n```markdown\n# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __\n```\n\n*→ Method in Action: [Fisher and Ury, 1981 — The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md)*\n\n## Pack: BATNA & ZOPA Patterns\n\n| Negotiation | Your BATNA | Their BATNA |\n|---|---|---|\n| Term sheet | Other investors / bridge / status quo | Other pipeline deals |\n| Salary | Other offers, current job, savings runway | Next candidate, leave role open |\n| Vendor contract | Other vendors, build in-house, defer | Other customers, lower revenue |\n| M&A | Continue independent, alternative acquirer | Build in-house, acquire competitor |\n\n## Applying It Well\n\n- Compute BATNA *before* any negotiation session — mid-session computation is slow and biased\n- Model their BATNA with the same rigor as your own — it sets your ceiling\n- Multi-issue deals: identify what each side values most and trade across variables\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My BATNA is strong\" without specifics | Where exactly, with what offer, by when? If you can't answer, BATNA is weak. |\n| [D] No estimate of their BATNA | Their BATNA caps your aspiration — without it you over-ask or under-ask. |\n| [D] ZOPA non-existence = \"they're being difficult\" | Sometimes no deal exists. Structural change, not harder negotiation. |\n| [D] Splitting the difference | Signals you have room. Make small concessions instead. |\n| [D] Walking at aspiration, not reservation | Walking early leaves money on the table. |\n| [D] Staying past reservation (sunk costs) | Negotiation effort is irrelevant. If deal < BATNA, walk. |\n| [D] Bluffing about BATNA | If discovered, credibility collapses. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"My BATNA is going elsewhere\" without specifics — No estimate of their BATNA\n- Pressure to close before BATNA computation is done — ZOPA not explicitly checked\n- Reservation price not pre-committed before negotiating\n\n## Verification\n\n- [ ] BATNA: specific alternative, value, timeline, risk-adjusted\n- [ ] Reservation > BATNA (with buffer); opening > aspiration\n- [ ] Their BATNA estimated with reasoning; ZOPA checked\n- [ ] If no ZOPA: structural move identified\n- [ ] If ZOPA: opening, concession pattern, walk-point pre-committed\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782451079313\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n\nFile v1.0.0:examples/fisher-and-ury-1981-the-harvard-negotiation-project.md\n\n# Method in Action: Fisher and Ury, 1981 — The Harvard Negotiation Project\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe framework's primary source is Fisher and Ury's *Getting to Yes*, which emerged from research at the Harvard Negotiation Project (founded 1979). Fisher had been a US negotiator and Harvard Law professor; Ury was a young anthropologist (later co-founder of the Program on Negotiation at Harvard). Their goal: distill a method of negotiation that was both ethical and effective — better than positional bargaining (each side haggling toward the middle) and better than soft accommodation (giving in to preserve the relationship).\n\nThe book introduced four principles of \"principled negotiation\": separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria. **BATNA was the framework's bedrock concept** — without it, none of the other principles work, because you have no standard against which to evaluate proposed agreements.\n\nFisher and Ury's central passage on BATNA:\n\n> \"The better your BATNA, the greater your power. Whatever the merits of a particular proposal, you can always walk away from it; the question is whether walking away — that is, your BATNA — is a real and attractive option. People think of negotiating power as being determined by such resources as wealth, political connections, physical strength, friends, and military might. In fact, the relative negotiating power of two parties depends primarily upon how attractive to each is the option of not reaching agreement.\"\n\n— Fisher & Ury (1981/1991), pp. 102-103.\n\nThe empirical foundation of the framework was Fisher's own diplomatic experience (he had been involved in US-Iran hostage negotiations, Camp David Accords mediation, and various international conflict-resolution efforts) plus the case-study collection assembled at the Negotiation Project. The framework was tested in subsequent decades across business, diplomacy, labor disputes, and litigation; the consistent finding has been that **negotiations where parties explicitly identified BATNAs produced better outcomes for both sides** than negotiations conducted from positional bargaining.\n\nSubsequent refinements have come from Lax & Sebenius (1986, *The Manager as Negotiator*), Mnookin (2000, *Beyond Winning*), and Malhotra & Bazerman (2007, *Negotiation Genius*). The BATNA / ZOPA framework remains the standard starting vocabulary in MBA negotiation courses, executive education, and serious deal practice.\n\nSeveral operational lessons from 40+ years of application:\n\n**First, most negotiators dramatically over-rate their own BATNA and under-rate the counterparty's.** This produces overconfident asks that produce no-deal outcomes. The corrective is rigorous, specific BATNA computation (Step 1) — not vibes.\n\n**Second, BATNA strengthening usually beats tactical sophistication.** A negotiator with a weak BATNA but great tactics typically loses to a negotiator with a strong BATNA and average tactics. **The single most powerful negotiation move is often to walk away from the table to strengthen your BATNA, then return.**\n\n**Third, ZOPA non-existence is the most under-recognized situation.** Many negotiations fail not because the parties negotiated badly but because no deal was possible under the current structure. Recognizing this earlier saves enormous time and emotional energy.\n\n**Fourth, multi-issue negotiations almost always create more value than single-issue.** When parties value variables differently, trading creates surplus. Single-variable price negotiations are zero-sum; multi-variable negotiations are usually positive-sum.\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nGuides agents through BATNA and ZOPA analysis for non-trivial negotiations, including walk-away points, reservation prices, counterparty alternatives, and deal/no-deal strategy. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users and agents use this skill to structure salary, term-sheet, vendor, customer-pricing, partnership, and M&A negotiations by computing BATNA, reservation, aspiration, opening offer, counterparty BATNA, and ZOPA before deciding whether to proceed or walk away. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Negotiation guidance can be wrong if BATNA, reservation, or counterparty estimates are incomplete or biased. <br>\nMitigation: Use the skill's falsifier and verification checklist, validate assumptions against current deal evidence, and seek qualified legal, financial, or HR review for high-stakes negotiations. <br>\nRisk: The skill is text-only guidance, so its recommendations may not match a user's specific workflow or negotiation context. <br>\nMitigation: Review the SKILL.md guidance before deployment and adapt use to the user's jurisdiction, culture, organization policy, and deal constraints. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/batna-zopa) <br>\n- [Publisher profile](https://clawhub.ai/user/deciqai) <br>\n- [Sources - batna-zopa](references/sources.md) <br>\n- [Method in Action: Fisher and Ury, 1981 - The Harvard Negotiation Project](examples/fisher-and-ury-1981-the-harvard-negotiation-project.md) <br>\n- [Harvard Program on Negotiation](https://www.pon.harvard.edu/) <br>\n- [deciqAI](https://deciqai.com) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown analysis template with structured negotiation fields] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Text-only guidance; no executable code, credential access, persistence, or data exfiltration behavior found in security evidence.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: BATNA & ZOPA Owner: deciqai Summary: Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:52:27.725Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json) v1.0.4 | 2026-07-14T06:44:01.889Z | auto - A","codeSnippets":[],"executableExamples":[{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"},{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"},{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"},{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"},{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"},{"language":"markdown","snippet":"# BATNA & ZOPA Analysis: <deal>\n## My side:  BATNA <value> | Reservation $__ | Aspiration $__ | Opening $__\n## Their side: Est. BATNA <…> | Est. reservation $__\n## ZOPA: $__ to $__ | Exists? yes/no\n## Strategy: [if ZOPA] open at __; walk at __; concede via __\n##            [if no ZOPA] structural move: __\n## Falsifier: observation that would tell me my estimates are wrong: __"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: batna-zopa\ndescription: \"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-sheet/vendor/M&A negotiation where stakes are non-trivial. Do NOT activate when: the situation is a purely emotional relationship dispute with no transactional dimension; cultural context makes explicit BATNA discussion taboo. More: deciqai.com/c/batna-zopa\"\n---\n\n# BATNA & ZOPA\n\n## Overview\n\n**BATNA** (Best Alternative to a Negotiated Agreement) is the value of your best fallback if no deal happens — the floor below which you walk away. A negotiator without a clear BATNA negotiates from fear; with one, from position.\n\n**ZOPA** (Zone of Possible Agreement) is the overlap between what each side will accept. If it exists, a deal is possible; if not, the question is structural change — not harder negotiating.\n\nComposes with `anchoring`, `signaling-games`, `repeated-games-reputation`, and `prisoners-dilemma`.\n\n## When to Use\n\n- Any non-trivial negotiation: term sheets, salary, partnership, M&A, vendor contracts, customer pricing\n- You feel pressure to take a deal that \"feels bad\" — usually a sign your BATNA is weak or not modeled\n- Assess whether a deal *can* happen before investing time in tactics\n- Raising in the 2024–2026 AI market (term sheets, SAFEs) or committing to a GPU-cloud / compute contract, where FOMO and \"capacity is scarce\" pressure obscure your real alternative\n\n**Not when:** purely emotional/non-transactional disputes; cultures where direct BATNA discussion is taboo.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete deal → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: BATNA = your walk-away value; ZOPA = the range where both sides say yes.\n2. Check fit: relationship-only situations → point elsewhere.\n3. \"What negotiation are you in right now?\"\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: What's your BATNA? What's theirs? Where's the overlap?\n> **[WAIT — do not advance until user responds]**\n5. Name the specific opening offer and walk-away point they've identified.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Compute your BATNA:** specific alternative + dollar value + timeline + probability → risk-adjusted value. \"Going elsewhere\" is not a BATNA. Strengthen before negotiating (parallel processes, extended runway).\n\n**Step 2 — Set reservation & aspiration:** Reservation > BATNA (with buffer). Opening offer > aspiration, but defensible.\n\n**Step 3 — Estimate their BATNA:** Ask directly; research alternatives; observe behavior (patient = strong, pressured = weak). Their reservation caps your ceiling.\n\n**Step 4 — Find the ZOPA:** Overlap of reservation prices. If none exists → structural move"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"batna-zopa\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224347725\n}"},{"path":"references/sources.md","content":"# Sources — batna-zopa\n\n> *Primary sources for the [batna-zopa](../SKILL.md) skill.*\n\n- Fisher, R., & Ury, W. (1981/1991). *Getting to Yes: Negotiating Agreement Without Giving In* (2nd ed.). Penguin. ISBN 978-0140157352. The founding text; BATNA defined on pp. 99-108.\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. The first systematic extension into business negotiation. ISBN 978-0029187706.\n- Quandt, W. B. (1986). *Camp David: Peacemaking and Politics.* Brookings Institution. The definitive scholarly account of the 1978 Camp David negotiations — the framework's canonical diplomatic case.\n- Mnookin, R. H. (2000). *Beyond Winning: Negotiating to Create Value in Deals and Disputes.* Harvard University Press. The framework applied to legal and business disputes. ISBN 978-0674008830.\n- Malhotra, D., & Bazerman, M. (2007). *Negotiation Genius: How to Overcome Obstacles and Achieve Brilliant Results at the Bargaining Table and Beyond.* Bantam. Modern operational synthesis. ISBN 978-0553804881.\n- Harvard Program on Negotiation: https://www.pon.harvard.edu/ — continues active research and case-study development.\n- Feld, B., & Mendelson, J. (2019). *Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist* (4th ed.). Wiley. Standard reference for term-sheet mechanics (liquidation preference, option pool, pro-rata, board control) that make up the multi-issue ZOPA in a fundraising negotiation — used in the 2024–2026 AI term-sheet example. (Round sizes and valuations vary by deal and period; not asserted as specific figures.)\n- Lax, D. A., & Sebenius, J. K. (1986). *The Manager as Negotiator.* Free Press. https://www.pon.harvard.edu — the value-creation / multi-issue \"structural move\" applied when no single-issue (price-only) ZOPA exists, e.g. widening a valuation stalemate into a trade across preference, pool, and pro-rata."},{"path":"examples/ai-startup-term-sheet-and-compute-negotiation-2024-2026.md","content":"# Method in Action: An AI Startup's Term Sheet & Compute Contract (2024–2026)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe 2024–2026 AI funding market was bifurcated: a handful of \"hot\" AI startups fielded competing term sheets at rich valuations, while most founders negotiated from a weaker spot than the headlines suggested. BATNA/ZOPA cuts through the FOMO in both directions. This walks the five steps through a Series A raise, then a shorter compute-contract case — the two negotiations that most often decide an AI startup's fate. Figures are illustrative; the discipline is the point.\n\n### Case 1 — a Series A term sheet\n\n**Step 1 — Compute your BATNA.** A founder feeling flattered by one interested fund has no BATNA — \"they might pass\" is not an alternative. The real BATNA is concrete: *a second term sheet at $X*, or *18 months of runway at current burn that lets us raise later from a stronger revenue position*, each with a dollar value, timeline, and probability. The single highest-leverage move in the whole raise happens *before* any negotiation: run a **parallel process** so more than one fund is live at once, and extend runway so \"no deal now\" is survivable. A founder with 3 months of cash and one term sheet has, in effect, no BATNA — and the term sheet's terms will show it.\n\n**Step 2 — Set reservation & aspiration.** Reservation is the worst valuation/terms you'd still sign versus your BATNA — and terms are not just the number: liquidation preference, option-pool shuffle, board control, and pro-rata can swamp headline valuation. Aspiration is a defensible high anchor grounded in comparable 2024–2026 rounds, not a wish. Open above aspiration but justifiable.\n\n**Step 3 — Estimate their BATNA.** The VC's BATNA is *their next-best deal* plus the cost of missing a category winner. In a hot AI sub-sector, fund FOMO is real leverage *for the founder* — a fund that has already missed one breakout is negotiating against its own regret. Read behavior per the skill: a patient investor is signalling a strong BATNA (they have other deals); a fund pushing to sign before you can run your process is signalling a weak one (or is managing *your* BATNA down). Their reservation — the most dilution/price they'll accept — caps what you can get.\n\n**Step 4 — Find the ZOPA.** Overlap of the two reservation prices. If a fund's ceiling is below your floor, negotiating \"harder\" is wasted motion — make a **structural move** instead: add issues to trade (a smaller round at a better price + more pro-rata; a SAFE bridge to reach a metric that resets comps; a different lead). No ZOPA on valuation often has a ZOPA once you widen past the single number.\n\n**Step 5 — Distribute within the ZOPA.** Open at your favorable, defensible boundary (this composes with [anchoring](../anchoring/SKILL.md)). Concede in small steps; never \"split the difference\" reflexively. Trade variables — give on board observer seats to hold valuation, or accept a standard 1x non-participat"},{"path":"examples/camp-david-accords-sinai-1978.md","content":"# Method in Action: The Camp David Accords — Egypt, Israel, and the Sinai (1978)\n\n> *Example for the [batna-zopa](../SKILL.md) skill.*\n\nThe thirteen-day Camp David summit (September 5–17, 1978) between Egypt's Anwar Sadat and Israel's Menachem Begin, mediated by US President Jimmy Carter, is the canonical diplomatic demonstration of the framework. Fisher and Ury themselves use the Sinai dispute as the flagship example of \"focus on interests, not positions\" in *Getting to Yes*, and the summit's mediation process as the leading real-world application of the one-text procedure.\n\n**The BATNAs.** Israel had occupied the Sinai Peninsula since the 1967 war. For both sides, no-deal meant continued belligerency:\n\n- Egypt's fallback: keep bearing the economic and political cost of a lost peninsula, plus the standing risk of another war — the 1973 war was only five years past.\n- Israel's fallback: keep bearing the cost of occupation, permanent mobilization on the southern front, and mounting international isolation.\n\nBoth BATNAs were bad, specific, and mutually understood — which is precisely why both leaders accepted Carter's invitation. Weak BATNAs on both sides do not guarantee a deal, but they widen the potential ZOPA.\n\n**Reservation prices — and an apparent empty ZOPA.** On the single issue as first framed — *where to draw the line in the Sinai* — the reservation prices did not overlap. Egypt's stated position: every inch of the Sinai returns to full Egyptian sovereignty. Israel's stated position: retain part of the Sinai — settlements, airfields, strategic depth — as a security buffer. No line on the map satisfied both reservations. On positions alone, the ZOPA was empty, and years of positional bargaining had confirmed it.\n\n**The structural move.** The mediating team did not \"negotiate harder.\" It unbundled positions into interests:\n\n- Egypt's underlying interest was *sovereignty* — a matter of national dignity after centuries of foreign control. It did not need tanks on the border to have its flag on the territory.\n- Israel's underlying interest was *security* — no Egyptian armor massed within striking distance. It did not need to own the land to keep the buffer.\n\nThose interests were compatible even though the positions were not. The solution: the entire Sinai returns to Egyptian sovereignty, while large zones of it are demilitarized, with monitoring arrangements. Egypt got the flag; Israel got the buffer. Adding issues — phased withdrawal timelines, diplomatic normalization, evacuation of Israeli settlements and airfields, and US assistance to both parties — further expanded the deal space. This is Step 4's prescription executed at state scale: when no ZOPA exists, change the structure (reframe the issue, add variables), not the pressure.\n\n**Distributing within the new ZOPA.** Carter's team used the one-text procedure: the mediator drafts a single negotiating text, each side criticizes it, and the mediator revises through repeated rounds — rather "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Skill: BATNA & ZOPA Owner: deciqai Summary: Activate when: user says 'walk-away point', 'reservation price', 'should I take this deal', 'what's my leverage', 'they won't budge', or any salary/term-shee... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:52:27.725Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/batna-zopa.json) v1.0.4 | 2026-07-14T06:44:01.889Z | auto - A","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2088,"uniquenessScore":48,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T20:08:48.736Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-12T18:07:17.663Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}