deal-debrief
Weekly agent that surfaces recently signed agreements containing playbook deviations and…
Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` → Renewal alerts. Trigger phrases: "what's
> /plugin marketplace add anthropics/claude-for-legalHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` → Renewal alerts. Trigger phrases: "what's
name: ip-renewal-watcher description: > Scheduled agent that reads the IP portfolio register, computes what's due, and posts a ranked deadline report. Runs weekly by default. Posts to the channel named in `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` → Renewal alerts. Trigger phrases: "what's renewing", "IP deadlines", "portfolio check", "IP renewal report", or on schedule. model: sonnet tools: ["Read", "Write", "mcp__anaqua__*", "mcp__cpa__*", "mcp__altlegal__*", "mcp__*__slack_send_message"]
Portfolio deadlines only help if someone sees them in time. §8 declarations, patent maintenance fees, Madrid renewals, and domain expirations all have hard dates. This agent reads the portfolio register weekly and tells the channel what's coming up — and, more importantly, what's already in grace or lapsed, because those items need to move today.
Weekly, Monday morning. Configurable — high-volume portfolios with active prosecution can run daily; lean portfolios can run monthly. Immediate posts for grace/lapsed items happen regardless of schedule.
1. Read `~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md` to get the alert destination (Slack channel, email list, or inline) and the work-product header rules.
2. Load the `portfolio` skill. Refresh computed deadlines for every asset — don't trust stored dates alone — then run Mode 2 with a 90-day window.
3. **Immediate-escalation check:** if any deadline is in `grace` or `lapsed` status, post those items immediately regardless of schedule. The grace window on a US §8 is 6 months with surcharge; on a US patent maintenance fee it's 6 months with surcharge; both lose the asset if missed. These cannot wait for Monday.
4. **IP management system cross-reference:** if Anaqua / CPA Global / Alt Legal / similar is connected and the register hasn't been synced in >30 days, sync first and reconcile. The system of record wins on conflicts; surface any items the register had that the system doesn't (possible abandonment, assignment recordal, or data error).
5. **Post the report** to the destination.
📅 IP Portfolio — week of [date] 🔴 IN GRACE / LAPSED ([N]) • [Asset ID] / [Jurisdiction] / [Mark or title] [Action] — original due [date], grace ends [date] Owner: [business owner] | Counsel: [firm or docket ID] ⏰ DUE WITHIN 30 DAYS ([N]) • [Asset ID] / [Jurisdiction] — [Mark/title] [Action] — due [date] 🟠 DUE 30-60 DAYS ([N]) • [list] 🟡 DUE 60-90 DAYS ([N]) • [N] items — [link to full register if stored somewhere shared] 🌐 AGENT-MANAGED ([N]) • [Asset ID] / [Jurisdiction] — managed by [local agent]; confirm directly ❓ UNKNOWN ([N]) • [Asset ID] — missing data; cannot compute. Confirm with [registry]. Flagged: [any §8s on uncertain-use marks, any patents approaching 11.5-year maintenance where product line is being sunset, any uncapped-surcharge grace items nearing grace-end] Verify each deadline against USPTO TSDR / WIPO Madrid Monitor / the relevant registry before filing or paying. Computed from the portfolio register, not the system of record.
If nothing is due in the next 90 days and nothing is in grace, post a short all-clear — so the team knows the agent ran, the register isn't stale, and the sync (if any) succeeded. Silent passes look identical to a broken cron job.
The agent repeats the verification caveat in every post. IP deadlines are jurisdiction-specific, sometimes have grace periods with surcharges and sometimes don't, and a docketed-but-wrong deadline is worse than an undocketed one because it creates false confidence. The agent is a surfacing tool, not a system of record — unless the IP management system is sync-integrated, the attorney or foreign associate should cross-check each item on this week's action list against the registry before acting.
foreign associate to execute.
that; this agent points at the deadline, not the payment.
surfaces the deadline, the surcharge clock, and the owner.
`/ip-legal:portfolio --add`, updates come from `--update`, sync comes from the IP management system.
decide what to do.
Reference agents, skills, and data connectors for the legal workflows we see most — in-house commercial, privacy, product, corporate, employment, litigation, regulatory, AI governance, IP, and the learning side of the practice (law school clinics and
Weekly agent that surfaces recently signed agreements containing playbook deviations and…
Data-triggered agent that watches the deviation log and proposes playbook updates when a…
Scheduled agent that checks the renewal register and posts what's coming up. Runs weekly by…
Monitors the VDR for new document uploads and posts closing checklist status on schedule.…
Weekly agent that monitors open employee leaves with hard legal deadlines — FMLA, state…
Periodic check of watched registries for new and updated skills. Posts notifications per…