# Obligation extraction

A reusable skill the "Never miss an obligation in a signed contract" recipe pulls in. Add it once and every agent on the team can use it.

Identify every deliverable, payment term, reporting cadence, and deadline a signed contract creates.

## Method
1. Read the parsed contract text from the document-parsing skill.
2. Scan for language that creates an obligation: deliverables, payments, reports, notices, and recurring cadences.
3. For each obligation, capture what is owed, who owes it, and the due date or trigger.
4. Distinguish an obligation from background language that describes rights without creating a duty.
5. Exclude renewal-window language, which is tracked separately by the renewal-radar recipe.
6. Record the source clause for every obligation extracted.

## Rules
- Only extract obligations the contract text actually creates, never an inferred best practice.
- Renewal and notice-window dates are out of scope here, to avoid double-tracking with the renewal radar.
- What counts as an obligation versus background language (set on first run, then stored in memory).
- Every obligation must carry a source clause; an obligation without one is not published.

## Output
A list of obligations, each with description, owed-by, due date or trigger, and source clause, ready for the reconciliation pass.