kevanwee

Oblig Register — Development skill for Claude Code

Development community

Turn an executed contract into a dated obligations register: validated schema, deadline resolution with traces, .ics calendar export with reminders, and a Claude extraction skill.

How to install Oblig Register

This entry records only its repository, not the path inside it, so there is no exact command to give. Open kevanwee/oblig-register and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Oblig Register does

Turn an executed contract into a dated obligations register: validated schema, deadline resolution with traces, .ics calendar export with reminders, and a Claude extraction skill.

Alternatives in Development

Epic Publish — Publish a validated epic update back to the issue and local cache 243.5k ★
Validate Plan — You are tasked with validating that an implementation plan was correctly executed, verifying all success crite 10k ★
Internet Court Skill — The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 4.9k ★

README

oblig-register

Turn an executed contract into a dated obligations register. A validated YAML schema for "who must do what, by when, or else", deadline resolution with a trace, `.ics` export with reminders, and a Claude skill for the extraction step.

- id: non-renewal-notice
  obligor: Beta Manufacturing Pte Ltd
  obligee: Acme Cloud Pte Ltd
  category: renewal
  description: Last day to give notice of non-renewal
  clause_ref: "8.3"
  verbatim: "... unless either party gives written notice of non-renewal not less than ninety (90) days before the expiry of the then-current term."
  trigger:
    kind: relative
    relative: { anchor: expiry, days: 90, direction: before }
  consequence: Automatic renewal for 12 months
  lead_days: 45

$ obligreg -j SG resolve examples/sample-register.yaml
non-renewal-notice: Last day to give notice of non-renewal
clause 8.3: "... not less than ninety (90) days before the expiry ..."
anchor expiry: 2029-02-28
- 90 calendar day(s) = 2028-11-30
  => 2028-11-30

Why

Contract analysers extract clauses. None of them produce the thing an in-house team actually needs after signing: a register of obligations with dates that lands in a calendar with lead-time reminders. The auto-renewal nobody noticed, the insurance certificate that was due in 14 Business Days, the 120-day price-increase window: these are operational failures, not drafting failures, and they are avoidable with a spreadsheet that someone keeps. This is the spreadsheet, as data, with the arithmetic done.

What is in the box

Piece	What it does
`schema/register.schema.json`	JSON Schema for a register, generated from the pydantic model.
`obligreg validate`	Duplicate ids, obligors that are not parties, dangling anchors, missing quotations, malformed triggers.
`obligreg resolve`	Every deadline with a line-by-line trace. Relative triggers chain (`data-deletion` anchored on `data-return` anchored on `event:termination`). Bus