$ loading_
Generate weekly status-request email drafts to outside counsel across the active portfolio — markdown per matter, plus Gmail drafts when the MCP is available. Use when the user asks for OC status requests, weekly outside counsel check-ins, or wants per-matter status emails drafted from the portfolio log.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "oc-status" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/claude-for-legal/main/litigation-legal/skills/oc-status/SKILL.md 2. Save it as ~/.claude/skills/oc-status/SKILL.md 3. Reload skills and tell me it's ready
To run weekly, set a recurring reminder to invoke /litigation-legal:oc-status. Automated scheduling requires a scheduled-tasks integration, which is not bundled.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml, filter per default rules (or per flags).~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → outside counsel directive style, signer defaults, budget posture.matter.md + history.md, draft per-matter email.~/.claude/plugins/config/claude-for-legal/litigation-legal/oc-status/[YYYY-MM-DD]/[slug].md.~/.claude/plugins/config/claude-for-legal/litigation-legal/oc-status/[YYYY-MM-DD]/_summary.md — what ran, what was skipped and why.Writing the same status-request email to outside counsel every week across 5–15 matters is mechanical cognitive tax. The content is consistent per matter (status, decisions pending, budget check). The audience is consistent (OC lead partner). The tone is consistent (per house outside-counsel-directive style). A scheduled task drafts all of them; counsel reviews and sends.
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — the filtering and field source~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/matter.md — matter context (current posture, open questions)~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/[slug]/history.md — recent events to inform what to ask about~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → outside counsel directive style, signer name/email, budget postureDefault filter:
status != closedoutside_counsel.firm != null AND outside_counsel.lead != nullnext_deadline within 21 daysSkip matters that just had a status update in the last 10 days (no need to re-ping) and matters where outside_counsel.email is null (email addresses needed for Gmail draft; still produce markdown).
Flags:
--all → draft for every active matter regardless of recency--slug=[slug] → draft for one matter only (ad-hoc request)--no-gmail → skip Gmail draft creation even if MCP is availableEach email has the same skeleton; content is matter-specific.
Subject: per house convention (from ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md outside counsel directive style; fallback: [Matter: [matter name]] — Weekly status update)
Body skeleton:
[lead partner first name],
[One sentence opener — natural, matches house tone.]
Checking in on [matter name]. A few items:
1. **Status since [date of last update captured in history.md]** — what's moved, what's pending? Any filings, hearings, correspondence, or calls since we last touched base?
2. **Upcoming deadlines** — I show [next_deadline from log + any deadlines in matter.md]. Confirm coverage plan and any dates we should add.
3. **Decisions pending** — [pull open questions from matter.md that require OC input; if none, omit this numbered item and renumber]
4. **Budget** — [monthly / quarterly / on-request per `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` budget posture]. Where are we against [budget authorization from matter.md]? Any variance to flag?
[If material and relevant: 5. Specific ask — e.g., "Please send me the latest draft of the motion to dismiss before [date]" — drawn from matter.md open questions.]
[Signoff — name, role, contact. From `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md` signer default for OC directives.]
…
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
Review an offer letter and any restrictive covenants — jurisdiction check included. Substantive rules (covenant enforceability, pay-transparency, salary-history limits, exemption criteria) are researched per hire, not stored. Use when the user says "review this offer", "can we use a non-compete here", "check this offer letter", "hiring in [state]", or attaches an offer.
Draft an audience-specific summary from the privileged investigation memo — HR, leadership, or outside counsel versions. Use when an investigation memo needs to be communicated to an audience that should not see the full privileged work product.
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
Read VDR documents and extract issues per house categories and materiality thresholds, producing findings in house memo format. Use when user says "review the data room", "extract issues from [folder]", "diligence review", "what's in the VDR", or points at VDR documents.