skills/mediation-dispute-analysis-jinzhe-tan/SKILL.md
Use this skill whenever a lawyer or mediator needs help analyzing a dispute for mediation purposes. This includes: reviewing case materials (pleadings, contracts, correspondence, evidence) to identify issues in dispute, summarizing each party's position and interests, conducting legal analysis of the key issues, proposing mediation strategies or settlement directions, and preparing for mediation sessions. Trigger this skill when the user mentions 'mediation', 'dispute analysis', 'settlement', 'dispute resolution', 'identify issues in dispute', 'party positions', 'mediation brief', 'case analysis for mediation', 'ADR', 'mediation preparation', 'caucus strategy', 'settlement options', or any request to analyze a conflict between two or more parties with the goal of finding resolution. Also trigger when the user uploads case files and asks for a structured breakdown of who wants what, what the core disagreements are, or how the case might settle. Even if the user doesn't explicitly say 'mediation', trigger when the context involves analyzing opposing positions in a dispute with a resolution-oriented (rather than litigation-oriented) goal.
npx skillsauth add lawvable/awesome-legal-skills mediation-dispute-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps lawyers and mediators rapidly analyze case materials to produce a structured dispute analysis — identifying the core issues, each party's position and underlying interests, relevant legal principles, and potential directions for mediation or settlement.
The skill is designed for civil and commercial disputes of all kinds: contract disputes, business disagreements, property conflicts, employment issues, consumer claims, and more. It takes a resolution-oriented approach, focusing not just on legal rights but on practical paths to agreement.
Mediation, at its core, is negotiation between disputing parties assisted by a neutral third party. Unlike arbitration or litigation, the mediator has no decision-making power — the parties themselves craft their resolution. This skill helps the lawyer or mediator prepare the analytical groundwork that makes that resolution possible.
| File | Description |
|------|-------------|
| assets/mediation_report_template.docx | Professional Word template for formal mediation analysis reports. Use when the user requests a .docx output. The template includes a title page, all six analysis sections with placeholder text, formatted tables for issues and interests, BATNA/WATNA comparison table, and a readiness checklist with checkboxes. |
| File | Description |
|------|-------------|
| references/MEDIATION_PROCESS.md | Comprehensive mediation process guide covering core principles, the 12 stages of mediation, mediator and counsel roles, power imbalance strategies, and mediation agreement checklist. Consult when you need deeper context on mediation procedures or best practices. |
| references/NEGOTIATION_CONCEPTS.md | Quick reference for analytical concepts: positions vs. interests, BATNA/WATNA analysis, ZOPA identification, interest-based negotiation framework, settlement option patterns, and impasse-breaking techniques. Consult when building the strategy and settlement sections of the analysis. |
Read the relevant reference file when you need more depth on a specific topic. You do not need to read both files for every case — use them as needed based on the complexity of the dispute.
A mediator or lawyer preparing for mediation faces a common challenge: they receive a stack of materials — pleadings, contracts, emails, invoices — and need to quickly distill the essence of the dispute. What exactly do the parties disagree about? What does each side really want? Where is there room for compromise? This skill automates the analytical heavy lifting so the lawyer can focus on strategy and human judgment.
Good mediation preparation means understanding not just the legal positions, but the underlying interests, the relationship dynamics, and the practical constraints each party faces. The goal is to move beyond legal concepts like fault and toward a shared understanding of each party's actual needs — which is what makes mediated outcomes more durable than imposed ones.
The skill supports two workflows depending on how the user approaches it:
Use this mode when the user hasn't provided case materials upfront, or when materials are incomplete. Walk the user through a structured intake process before generating the analysis.
Use this mode when the user has already provided all relevant case materials (uploaded files, pasted text, or detailed description). Skip the intake and go straight to analysis.
How to decide: If the user uploads files or provides a detailed case description in their first message, use Mode B. If they say something like "I have a mediation case" or "help me prepare for mediation" without providing materials, use Mode A.
Ask the user for the following in a natural, conversational way:
Essential Information:
Prompt example:
"To prepare a thorough dispute analysis, I'll need to understand the case. Could you tell me:
- What type of dispute is this (e.g., contract, employment, commercial)?
- Who are the parties and what's their relationship?
- What happened — the key facts and timeline?
- What's the current status — has litigation started, or is this pre-suit?
Feel free to share as much detail as you have. You can also upload any case documents (pleadings, contracts, correspondence) and I'll extract the relevant information."
Based on the initial information, ask targeted follow-up questions:
Adapt these questions to the specific case — not all will be relevant every time.
Once sufficient information is gathered, proceed to the Analysis Framework below.
When the user provides case materials upfront, read and analyze them thoroughly before generating output. Materials may include:
| Material Type | What to Extract | |---|---| | Pleadings / Written statements | Each party's factual claims, legal arguments, and requested remedies | | Contracts / Agreements | Relevant clauses, obligations, breach allegations, ambiguous terms | | Correspondence (emails, letters) | Timeline of events, admissions, tone/relationship dynamics, negotiation history | | Evidence (invoices, photos, reports) | Supporting facts, quantum of damages, credibility indicators | | Prior settlement communications | Previous offers, rejected proposals, areas of near-agreement |
After reviewing materials, proceed directly to the Analysis Framework.
This is the core of the skill. Whether information was gathered through Mode A or Mode B, the output follows this structure:
Write a concise, neutral factual summary (typically 1-2 paragraphs). This should:
Identify and list each discrete issue the parties disagree about. For each issue:
Issue [Number]: [Descriptive Title]
Organize issues by significance — the most important or valuable issues first.
Typically there are 2-6 core issues in a dispute. If you identify more than 6, consider whether some can be grouped. If there appears to be only 1, look more carefully — there are usually sub-issues worth separating out (e.g., liability vs. quantum, or different breach allegations).
After listing individual issues, suggest a sequence for addressing them in mediation. Consider starting with issues where agreement seems most achievable to build momentum, or starting with the most critical issue if the parties need to see progress on the core problem before engaging on peripheral matters. Note the reasoning behind the recommended sequence.
This section goes beyond legal positions to identify what each party actually needs or wants. Understanding interests rather than just positions is what makes mediated outcomes possible — and more durable than imposed ones.
Party A's Interests:
Party B's Interests:
Shared or Compatible Interests:
Potential Barriers:
For each key issue, provide a brief legal analysis. This should:
The legal analysis should be practical and outcome-oriented — focused on helping the user understand the litigation risk landscape, not providing an academic treatise. The point is to inform the mediation strategy: parties who understand their litigation risk are better positioned to make rational settlement decisions.
Important: If the user specifies a jurisdiction, tailor the legal analysis accordingly. If no jurisdiction is specified, apply widely recognized common law and civil law principles and note that jurisdiction-specific advice should be sought.
This is the most valuable section for the user. Provide:
BATNA/WATNA Analysis:
Zone of Possible Agreement (ZOPA):
Proposed Settlement Directions: Present 2-3 concrete settlement scenarios, ranging from conservative to creative:
For each scenario, briefly note:
Process Recommendations:
Recommend a mediation format and approach based on the case characteristics:
Provide a tailored checklist based on the specific case. Draw from these items as relevant:
Parties & Authority:
Process Design:
Preparation:
Not all items will apply to every case — include only what is relevant.
Present the analysis directly in the conversation using clear headings and the structure above. This is appropriate for most cases and allows for easy follow-up discussion.
If the user requests a formal document (or if the analysis is lengthy/complex), generate a professional Word document using the template at assets/mediation_report_template.docx as a structural reference. Use the docx skill for document creation.
Start from the template's structure and replace all placeholder text with the actual analysis content. The template provides:
Adapt the template to the specific case:
Always include a brief disclaimer at the end of the analysis:
This analysis is prepared to assist in mediation preparation and does not constitute legal advice. It is based solely on the materials and information provided. A qualified legal professional in the relevant jurisdiction should be consulted for jurisdiction-specific legal advice. This document is confidential and prepared for mediation purposes only.
tools
Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.
development
Professional Excel spreadsheet creation with a focus on aesthetics and data analysis. Use when creating spreadsheets for organizing, analyzing, and presenting structured data in a clear and professional format.
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
tools
Build VS Code extensions from scratch or convert existing JS/React/Vue apps. Supports commands, webviews (React/Vue), custom editors, tree views, and AI agent integration via file-bridge IPC. Use when user wants to create a VS Code extension, convert a web app to an extension, add webviews or custom UIs to VS Code, implement tree views, build custom file editors, integrate with AI agents, or package/publish extensions (.vsix).