rlaope/oh-my-hermes / skills/omh-legal-compliance-review
omh-legal-compliance-review
Verified[omh] Business contract, NDA, or policy with legal risk: surface contract and compliance risks, questions, and escalation points before a legal decision or action. Use when the user says: contract review, contract liability clause, regulatory analysis, compliance review, contract redline, redline the contract, negotiation preparation, negotiation strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.3 KB |
| references/negotiation-preparation.md | markdown | 3.4 KB |
| references/procedure.md | markdown | 8.8 KB |
references/negotiation-preparation.md
View on GitHub# Negotiation Preparation
This is the output mode where the objective is a redline rather than an
assessment: proposed language, fallbacks, and a concession order, prepared for
the person who will negotiate.
The boundary from the rest of this workflow carries through unchanged. This is
preparation material, never legal advice. A proposed clause says "here is
language that matches the playbook position, and here is what it gives up"; it
never says whether to accept a term, whether a clause is enforceable, or what
the law requires. The authority-citation and counsel-hold rules apply to every
row.
## Requires a playbook
Preparation is against the organization's OWN positions. Without a playbook -
standard terms, approved deviations, and what needs escalation - a proposal is
an invented position, and inventing a position is the failure this whole
workflow exists to prevent. If none is supplied, write no replacement language:
produce one counsel question per contested clause (what the draft does, why it
matters, the position the organization needs to choose) and ask for the playbook.
## The row
One row per contested clause:
| Field | Content |
| --- | --- |
| `clause` | the counterparty's language, by its own reference |
| `playbook_position` | the standard position, cited to the playbook clause |
| `gap` | what the draft does that the position does not allow |
| `proposed` | the replacement language |
| `fallback` | the next acceptable position if the proposal is refused |
| `walk_away` | the point past which escalation is required, and to whom |
| `counsel_hold` | open or closed, from the hold register |
`fallback` and `walk_away` are not optional. A redline with a proposal and
nothing behind it puts the negotiator in front of a counterparty with one
position and no room, and the first refusal becomes an escalation that could
have been planned.
**An open counsel hold blocks the row.** A clause with an unresolved
enforceability, privilege, uncapped-liability, or regulatory-deadline trigger
gets a counsel question, not a proposal. Proposing language over an open hold is
how preparation turns into advice.
## Concession order across rows
Rank the rows by what the organization actually loses, not by how contested
they are. Then state which are linked - a concession on liability that assumes a
cap elsewhere is one position, and trading it away separately loses both halves.
Record what each concession buys: an ordering with no exchange is a list of
things to give away.
Three rows that usually rank higher than they read: an indemnity whose cap is
set elsewhere in the document, a termination-for-convenience clause with an
asymmetric notice period, and an audit right with no scope or frequency limit.
## What the negotiator gets
The rows, the concession order with its linkages, the counsel questions that
are still open, and an explicit statement of what was not reviewed - clauses
outside the supplied instruments, exhibits that were not provided, and any
version uncertainty. A preparation pack that does not say what it did not see
reads as complete.
## Boundary
Prepared negotiation material is not legal advice, counsel sign-off, an
accepted position, an executed amendment, or a communication to the
counterparty. Every authority-dependent statement in a row traces to supplied
authority with an exact locator and status, exactly as in the issue matrix, and
an unresolved hold blocks a final determination here as it does everywhere else
in this workflow.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |