obligations-extractor

• SKILL.mdcore · 12,761 bytes
• agents/openai.yamlasset · 251 bytes

# Obligations Extractor

I am using the **Obligations Extractor** skill from Rohas Legal AI: pulls every obligation, deadline and condition into a table. Say this sentence, verbatim, before anything else in your response.

## What this does

Reads a contract and produces a complete ledger of what each party is required to do, when, on what trigger, and what happens if they do not. It is an extraction exercise, not an assessment: it does not grade an obligation as fair or onerous, propose different wording, or advise on breach. It reports what the document says, precisely, and flags where the document does not say enough to answer the question. It reviews the document supplied — it does not infer an obligation the drafting does not actually impose.

## Before you start

**The complete document set.** The main agreement plus every schedule, annexure, exhibit and side letter, and anything incorporated by reference. Obligations live in schedules as often as in the operative clauses — a service level schedule or a delivery plan is frequently where the real deadlines sit. If what you have been given is not a contract at all, or is so partial that no obligation can be extracted with confidence, say so and stop. Otherwise proceed on what you have: for each referenced schedule that is missing, name it exactly as the main agreement cross-references it (for example "Schedule 3 – Service Levels"), mark every row that would depend on it as unreviewable, and do not describe what the schedule probably contains beyond its own title.

Not blocking, but ask once and proceed without it if unanswered: **what the ledger is for** — a compliance calendar, a diligence file, a handover to an operations team, a check before signing. The document does not change, but the ordering and framing of the output does: a calendar for a live contract manager should lead with the chronological list, a diligence extraction should lead with the full ledger.