agentleFS
shangyiyshangyiy/life-kit/skills/work/negotiation/SKILL.md

negotiation

Skill10 starsChanged 6 days agoMITView on GitHub

Reach an agreement that serves the important interests of the people involved, or see when no agreement is better. Use when your interests differ from another party's over terms, scope, time, resources or arrangements, or on /negotiation.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    The aim is alignment: Look for terms that serve both sides' important interests better than what each could do without a deal.

    line 22
  2. Very specific:

    Define your interests: Use /purpose to state the outcome you want.

    line 35
  3. Very specific:

    Understand the other party: Use /perspective to learn what they want, what they answer for, their limits and incentives, and who can decide.

    line 38
  4. Distinctive:

    Ask before you propose, and list what you still assume.

    line 41
  5. Very specific:

    Know the alternatives: Use /optionality to judge what happens with no deal, your best alternative and how strong it is, and theirs.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/negotiation

Reach an agreement that serves the important interests of the people involved, or see when no agreement is better.

Principles

  • Interests, not positions. Each side states a position, but what it needs is the interests behind it. A position is one way to meet them; there are usually others.
  • The aim is alignment. Look for terms that serve both sides' important interests better than what each could do without a deal. If no such terms exist, no deal is the right result.
  • Differences make trades. Sides weigh issues, risk and timing differently. Those gaps let each give what costs it little and gain what matters to it.
  • Honest, not open. Protecting information is fine; deceiving is not. Do not bluff about alternatives or invent someone you must consult.
  • A deal is what both will keep. Agreed terms count only as commitments each side can realistically honor.

How to negotiate

  1. Define your interests. Use /purpose to state the outcome you want. Sort what you want into essential, important and tradeable, and set a first minimum.
  2. Understand the other party. Use /perspective to learn what they want, what they answer for, their limits and incentives, and who can decide. Ask before you propose, and list what you still assume.
  3. Know the alternatives. Use /optionality to judge what happens with no deal, your best alternative and how strong it is, and theirs. Revise your minimum to match. If your alternative is weak, improve it or buy time before you commit. Then decide whether it is worth negotiating at all: weigh what is at stake against the cost to the relationship and the risk of asking.
  4. Create options. Find several ways to meet both sets of interests, trading across issues and testing them against fair outside standards. A proposal may be a package, or a different deal, such as smaller scope or a first step that lowers their risk.
  5. Evaluate and negotiate. Compare each proposal with your interests and alternatives. Know what a concession costs you and what it gives them. Ask the reasons behind an objection, and give a true reason with each request. Share your interests and reasons; keep your minimum and alternatives to yourself unless sharing them helps. Agree when each side will decide, leaving time to judge the whole before you accept or refuse. Where future results are uncertain, use /experimentation for a limited pilot, milestones or conditional terms.
  6. Commit or walk away. Confirm the terms in writing, with the assumptions left. Name responsibilities, deliverables, dates and who decides. Set review points and what reopens the deal. If the terms miss your minimum, decline and turn to your best alternative.

Output

  • Your interests, minimum and best alternative, and whether negotiating was worth it.
  • Their interests, limits, who decides, and unchecked assumptions.
  • The options weighed and the terms agreed, in writing.
  • Responsibilities, deliverables, dates, decision rights and review points.
  • The decision: agree, or no deal, and the next message.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.