SkillVaultskills Browse all 500 skills

Legal Operations · Version 1.3.0 · Reviewed 2026-08-02

Contract Obligation Tracker

Make review more traceable for obligation extraction and owner assignment with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Extracts ongoing obligations from executed contracts and assigns them to owners with review dates.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Obligation extraction
  • Owner assignment
  • Review scheduling

How Contract Obligation Tracker works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for obligation extraction

It decides

A owner assignment gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

What it checks first

Contract Obligation Tracker extracts ongoing obligations from executed contracts and assigns them to owners with review dates. Use it when the work involves Obligation extraction, Owner assignment, Review scheduling.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Decompose the document into obligations and changed rights
  2. Map each item to business impact, owner, and evidence
  3. Separate administrative changes from material risk
  4. Route unresolved legal judgment to qualified counsel

Deliverables

  • Obligation extraction matrix
  • Owner assignment escalation register
  • Review scheduling owner and evidence checklist

Evidence requirements

  • Contract, policy, clause library, or control inventory
  • Approved fallback language and escalation rules
  • Dates, owners, business context, and source version

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We have 200 signed customer contracts and no idea which ones contain commitments we are currently breaching.

Expected output

The obligations that get breached are the ongoing ones, since one-time terms complete at signing. Extract recurring commitments such as uptime, notification, audit rights, and retention, then assign each to a system owner with a verification date...

Boundaries and compatibility

Ideal for

  • Obligation extraction: produce a decision or artifact grounded in supplied evidence.
  • Owner assignment: produce a decision or artifact grounded in supplied evidence.
  • Review scheduling: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Providing legal advice or determining enforceability
  • Approving contracts, waivers, or regulatory positions

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.