negotiation-prep
/negotiation-prep
Prepare for and run a negotiation with structure: BATNA and ZOPA analysis, counterparty analysis, a 6-dimension score for any draft message, a pre-send checklist, and a concession ledger across rounds. Use for salary offers, vendor and supplier contracts, billing disputes, partnership terms, and any deal where the next message matters. Triggers: "prepare for the negotiation", "what's my BATNA", "analyze their position", "score this message", "review before I send", "draft a counter-offer", "is this a trap", "track concessions", "negotiation", "counter-offer", "deal terms".
- Author
- getedgehq ↗
- Repository
- skills ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Prepare for and run a negotiation with structure: BATNA and ZOPA analysis, counterparty analysis, a 6-dimension score for any draft message, a pre-send checklist, and a concession ledger across rounds. Use for salary offers, vendor and supplier contracts, billing disputes, partnership terms, and any deal where the next message matters. Triggers: "prepare for the negotiation", "what's my BATNA", "analyze their position", "score this message", "review before I send", "draft a counter-offer", "is this a trap", "track concessions", "negotiation", "counter-offer", "deal terms".
Triggers from the description
Original author description
Prepare for and run a negotiation with structure: BATNA and ZOPA analysis, counterparty analysis, a 6-dimension score for any draft message, a pre-send checklist, and a concession ledger across rounds. Use for salary offers, vendor and supplier contracts, billing disputes, partnership terms, and any deal where the next message matters. Triggers: "prepare for the negotiation", "what's my BATNA", "analyze their position", "score this message", "review before I send", "draft a counter-offer", "is this a trap", "track concessions", "negotiation", "counter-offer", "deal terms".
How it works
- Hard rule
- Core Workflow
- Key Principles
- References
SKILL.md preview
--- name: negotiation-prep description: >- Prepare for and run a negotiation with structure: BATNA and ZOPA analysis, counterparty analysis, a 6-dimension score for any draft message, a pre-send checklist, and a concession ledger across rounds. Use for salary offers, vendor and supplier contracts, billing disputes, partnership terms, and any deal where the next message matters. Triggers: "prepare for the negotiation", "what's my BATNA", "analyze their position", "score this message", "review before I send", "draft a counter-offer", "is this a trap", "track concessions", "negotiation", "counter-offer", "deal terms". --- # Negotiation Prep Structured preparation and message review for negotiations where the next move matters. Inspired by the negotiation preparation approach taught in the CEMS Negotiation Strategy course at Nova SBE. ## Hard rule - **Never reveal the user's BATNA**, walk-away point or reservation price in any draft, directly or by implication. - **Never state a fact that has not been verified.** If a number, date, clause or claim is not in the user's material, mark it as an assumption and ask. Do not invent market data, precedents or "industry standard" figures. ## Core Workflow ### 1. Context Loading Before any analysis, establish: - Who are the parties, and what is their relationship (one-off or repeated)? - What has been agreed so far? Look for written evidence: messages, emails, contracts, offer letters. - What is in dispute, and what is not yet on the table? - Which channel is this on? (chat = concise, email = structured, call = flexible) - What is the timeline? Deadlines, meetings, renewal dates, external events. Ask for the actual documents if they exist. If the user keeps a negotiation log in the working directory, read it first. State any assumption you make. ### 2. Mode Selection Pick the mode from the request. If unclear, ask, or default to PREPARE. **ANALYZE** - "analyze their position", "what do you make of this" - Read the counterparty's message or position - Detect contradictions across rounds - Separate position (what they say) from interest (what they need) - Assess power dynamics - Flag emotional vs. rational arguments - Output: structured analysis with actionable insights **SCORE** - "score this", "review before I send" - Apply the 6-dimension rubric (see [references/framework.md](references/framework.md)): Information Leakage, Anchoring, Tone, Logic, Leverage, Trap Detection - Score 1-10 per dimension plus overall - Quote the specific phrases that are problematic - Suggest a concrete rewrite for each flagged phrase - Output: score card + fixes + a rewritten version if the overall score is below 8/10 **DRAFT** - "draft a reply", "write a counter-offer" - Structure: opening (sets tone) + substantive points + close - Concede from your own anchor, never from theirs - Run SCORE on your own draft before presenting it - Output: ready-to-send message + score + rationale for the key choices **TRACK** - "what have I conceded", "where do we stand" - Build or update the concession ledger across all rounds - Net position: given vs. received - Flag concession fatigue (giving more per round) - Identify remaining leverage and room to move - Output: concession table + strategic assessment **PREPARE** - "prepare for the call", "what's my strategy" - BATNA and ZOPA analysis for both sides (see [references/framework.md](references/framework.md)) - Points to raise vs. points to hold back - Likely counterarguments and prepared responses - Walk-away line and fallback positions - Output: one-page prep doc with talking points and red lines ### 3. Pre-Send Gate Before any message goes out, run the checklist: 1. INFORMATION: Am I revealing anything usable against me? 2. ANCHORING: Am I reinforcing my frame or theirs? 3. ROOM: Do I have space to move if they push back? 4. TONE: Would this read well if a neutral third party saw it? 5. OMISSIONS: Is anything conspicuously absent that I want to stay absent? 6. CONTRADICTIONS: Does this contradict my position elsewhere? 7. INVITATION: Am I inviting a response I don't want? 8. TIMING: Is now the right time to send it? ## Key Principles - **Never reveal your BATNA.** The moment they know your alternative, they price it in. - **Never open at your final number.** Leave room to concede to where you actually want to land. - **Separate the people from the problem.** Firm on substance, warm on the relationship. - **What is not said matters.** If a clause that favors you is missing from their draft, you do not have to point it out. - **Every concession needs a trade.** Never give something for nothing. - **Detect false urgency.** "We need to close today" usually means they need to close today. - **Watch for position shifts between rounds.** A sudden change in tone often means they consulted someone. - **"Standard" is not an argument.** Ask for specifics, or argue the substance instead. ## References - **Scoring rubric, BATNA/ZOPA templates, concession ledger, pre-send checklist**: [references/framework.md](references/framework.md) - **Worked examples and anti-patterns**: [references/examples.md](references/examples.md)
Files in this package (5)
- DERIVATION.json 2 KB
- LICENSE 11 KB
- SKILL.md 5 KB
- references/examples.md 4 KB
- references/framework.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · getedgehq/skills | 100 | Apache-2.0 |
| varunk130/ai-strategic-partnerships-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 86bad1328cb6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90negotiation-expert
Prepares a negotiation: BATNA, anchors, concessions, scripts and walk-away point. Use before a sales deal, investor term negotiation, vendor contract, salary or partnership talk, or when the user asks how to respond to an offer. - 100batna-zopa
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… - 100ops-negotiation
Apply principled negotiation using BATNA, ZOPA, and the Harvard method to prepare for and conduct negotiations. Use this skill when the user needs to prepare for a negotiation, evaluate their bargaining position, design win-win solutions, or handle difficult negotiation… - 100plan-negotiation
Prepares a negotiation plan for one supplier - objectives, opening, target and walk-away positions, the buyer's best alternative and an evidence-based estimate of the supplier's, levers and trade-offs, concession sequence, anticipated supplier arguments with responses, and roles… - 100negotiation-concession-planner
Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-them, tiered, each give paired with a required reciprocal get and its approval level, plus a BATNA-based walk-away. Covers B2B (terms, scope,… - 90negotiation
Deal intelligence skill for offer analysis and counter-proposal drafting. Trigger on `review this offer`, `analyze counter`, `value gap`, `draft counter`, `should I walk`. Apply when reviewing any offer (real estate, compensation, vendor, resource allocation) or designing…