| name | track-deadlines-and-signatures |
| title | Track Deadlines and Signatures |
| description | Keep tabs on what's outstanding on the legal side. Pick what you need: chase pending signatures, log a freshly signed agreement, see what deadlines are coming up, or get a Monday rollup of the week. I keep a running list so nothing slips. |
| author | gethouston |
| author_url | https://github.com/gethouston/houston/tree/main/store/agents/legal/.agents/skills/track-deadlines-and-signatures |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | contracts |
| language | en |
Track Deadlines and Signatures
One skill for every standing-state tracker agent maintain. scope param pick tracker; atomic read-merge-write discipline shared.
Parameter: scope
signatures - watch connected signing platform (DocuSign / PandaDoc / HelloSign) for outstanding docs. Draft polite reminders for laggards (never send). File executed copies to connected doc-storage (Google Drive / Dropbox / Notion). Write status board to signature-status/{YYYY-MM-DD}.md.counterparties - append executed agreement to counterparty-tracker.json at agent root. Fields: id, counterparty, agreementType, executedDate, effectiveDate, term, autoRenewal, noticePeriod, governingLaw, keyObligations, renewalDate, signedCopyPath. Feed deadlines scope (renewal clock) + weekly-review scope (rollup).deadlines - seed + refresh canonical legal calendar. Static deadlines (Delaware March 1 annual report, 83(b) 30-day from grant, 409A refresh 12 months, DSR 30-day GDPR / 45-day CCPA, TM office action 6-month, annual board consent) + dynamic deadlines from counterparty-tracker.json (renewal clocks, notice windows). Write deadline-calendar.json at agent root + 90-day readout to deadline-summaries/{YYYY-MM-DD}.md. Flag ≤ 30 days urgent, overdue critical.weekly-review - aggregate across agent by reading outputs.json: what shipped this week (contract reviews, drafts, audits, filings), what pending signature (from signature-status/ most recent), next deadline (from deadline-calendar.json), what flagged for attorney review (attorneyReviewRequired: true entries without resolution). Write weekly-reviews/{YYYY-MM-DD}.md.
If user name scope plain English ("chase signatures", "log this deal", "what's due", "Monday review"), infer. If ambiguous, ask ONE question naming 4 options.
When to use
- Explicit: "where are my signatures", "log {counterparty}'s executed {type}", "what's due soon / overdue", "Monday legal review", "weekly legal readout".
