legal-compliance-obligation-extractionlisted
Install: claude install-skill alihusains/enterprise-skills
# Obligation extraction
## Purpose
Obligations get lost between the instrument and the register. Someone reads a
forty-page rule or a signed agreement, writes eight bullet points, and the
organisation tracks the bullet points forever — losing the conditions, the
carve-outs, the party that is actually bound, and the paragraph number a regulator
or a counterparty will cite. This skill produces the atomic register: one testable
duty per row, each traceable back to the provision it came from, so downstream
control mapping and evidence collection have something to attach to.
## Data classification
**Confidential, potentially privileged.** An obligation register is a list of what
the organisation is bound to do, and by implication where it may fall short.
Assume a regulator, counterparty or claimant may one day see it, and take a view
with counsel on whether it should sit under privilege.
**STOP CONDITIONS:**
| Trigger | Action |
| --- | --- |
| The instrument or the work relates to a live investigation, enforcement action, skilled-person review or litigation | Stop. Privilege and disclosure decisions come first. Route to counsel. |
| Counsel's advice, or without-prejudice correspondence, is pasted | Stop. Do not summarise or excerpt privileged material. |
| Customer, client or employee personal data appears in the source or as an illustration | Stop. Ask for it to be removed; extraction works on provisions, not records. |
| Client positions, balances, transactions or account