negotiation-conflict-resolution
Skill0 starsChanged 7 months agoMITView on GitHub
Find optimal solutions and reach consensus through negotiation in scenarios of resource conflict, priority disagreement, or changing requirements.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Seek Incremental Gains: Look for "bargaining chips" that are low cost to you but high value to the other party.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Negotiation & Conflict Resolution: Interests and Conflict Resolution
Negotiation is not about winning or losing, but about finding a third possibility.
Checklist
- Identify Underlying Needs (Interests vs. Positions) — Why does the other party insist on that solution? What do they really want?
- Prepare Alternatives (BATNA) — If negotiations break down, what is our bottom line and alternative plan?
- Apply Principled Negotiation — Set aside emotions and discuss based on objective criteria (e.g., metrics, cost, timeline).
- Record Consensus (The Deal) — Immediately confirm reached agreements in writing after the negotiation.
Expert Principles
- Empathy: Try to write the other party's "victory speech" and design your proposal accordingly.
- Separate People from Problems: Be tough on the issue, but soft on the person.
- Seek Incremental Gains: Look for "bargaining chips" that are low cost to you but high value to the other party.
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- product-vision-strategySkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.