From contract-negotiator
Autonomously negotiates .docx contracts: ingests docs, loads persona/authority/playbook configs, redlines clean docs or responds to changes without pauses.
npx claudepluginhub sarturko-maker/claude-plugin-mcpThis skill uses the workspace's default tool permissions.
Full-autonomy negotiation command. Same negotiation logic as `/negotiate` but
Reviews .docx contracts and produces redlined .docx with Track Changes for responding to counterparty markups or creating first-pass proposals.
Analyzes contracts for unfavorable clauses in liability, termination, IP, payment, and more; generates prioritized counter-proposals with market-standard replacements. Use for pre-signing reviews or negotiations.
Reviews contracts against negotiation playbook: flags deviations, generates redlines, analyzes business impact clause-by-clause. For vendor/customer agreements and strategy prep.
Share bugs, ideas, or general feedback.
Full-autonomy negotiation command. Same negotiation logic as /negotiate but
with all checkpoints removed. Claude reads the document, makes every decision
autonomously, and executes the full pipeline without stopping.
Configuration files (persona, authority, playbook) are still loaded and used to inform Claude's judgment -- they shape decision quality but never gate execution.
From the user's message, determine:
.docx fileDo NOT run a multi-step wizard. Extract what you can from the initial message. If something critical is missing, ask in one follow-up at most.
Follow the negotiate-contract skill's Step 1 for configuration loading. The three-level fallback applies:
PERSONA.md, AUTHORITY.md, PLAYBOOK-*.md,
LOA.md in the current working directory~/.config/claude-negotiator/defaults/ directoryIf no custom config exists, the defaults work out of the box. Users can
customise behaviour by placing PERSONA.md, AUTHORITY.md, or
PLAYBOOK-*.md files in their project directory or
~/.config/claude-negotiator/.
Call the ingest_document MCP tool with the document path. Then determine the
document type by checking the annotated text for CriticMarkup tracked change
markers:
{++ or {-- markers -- this is a clean document. A document
with only comment markers ({>>) but no tracked change markers is also
treated as clean.{++ or {-- markers present -- this document has existing tracked
changes.Follow the negotiate-contract skill's First-Pass Redlining Workflow (Steps A through H) with these modifications:
Follow the negotiate-contract skill's Counterparty Response Workflow (Steps 3 through 10) with these modifications:
/negotiate| Gate | /negotiate | /yolo-negotiation |
|---|---|---|
| Comparison report | Mandatory wait for confirmation | Shown inline, no wait |
| Authority zones (amber) | Pause and ask for guidance | Note in report, proceed |
| Authority zones (red) | Escalate immediately, do not act | Note in report, proceed |
| Supervised mode | Available for complex negotiations | Never offered |
All other negotiation logic is identical: materiality test, commenting rules, layering behaviour, edit precision, styler pass, and MCP tool usage.
| Tool | Purpose |
|---|---|
ingest_document | Read clean and annotated text views |
get_state_of_play | Get every change and comment with IDs |
execute_pipeline | Run the full negotiation pipeline (counterparty response) |
redline_document | Apply tracked changes to a clean document (first-pass) |
accept_changes | Accept specific tracked changes (granular) |
counter_propose_changes | Layer counter-proposals (granular) |
add_comments | Add standalone comments (granular) -- use ooxml:NNN anchors after mutations |
reply_to_comments | Reply to comment threads (granular) |
resolve_comments | Mark comment threads resolved (granular) |
Never reject a tracked change. Always layer counter-proposals on top of the counterparty's markup. The counterparty must see their original change alongside your response -- full audit trail, full transparency.