matter-update

Append dated litigation developments to matter history and synchronize portfolio log records.

109|20|Updated Mar 7, 2025
One-click install
npx skills add https://github.com/stakwork/stakgraph --skill matter-update-stakwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: matter-update
Source: https://github.com/stakwork/stakgraph/tree/main/mcp/skills/litigation-legal/matter-update
Command: npx skills add https://github.com/stakwork/stakgraph --skill matter-update-stakwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps litigation matter records current by capturing developments, updating status and risk information, and preserving a dated history without unmanaged or undocumented changes.

Core Features & Use Cases

  • Structured Event Capture: Records procedural, discovery, substantive, strategy, risk, stakeholder, and administrative developments.
  • Portfolio Synchronization: Updates the matter history file and corresponding portfolio log fields, including status, risk, materiality, exposure, deadlines, counsel, owners, and legal holds.
  • Safety and Review Gates: Requires the matter to exist in the managed log, prompts for materiality reassessment, and presents proposed history and YAML changes for confirmation before writing.
  • Use Case: After receiving a court order that changes the next deadline and litigation posture, use this Skill to append the event to the matter history and update the portfolio log for review.

Quick Start

Use the matter-update skill to record the latest development for a specified matter, including its event type, date, summary, and any affected portfolio fields.

Frequently Asked Questions about matter-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update litigation matter records and keep them audit-ready?

To update litigation matter records, append a dated development to the matter history and synchronize its portfolio log record. This captures procedural, discovery, and strategy updates while validating the matter slug and applying materiality review gates before writing changes.

What is the best way to track case history developments for managed litigation?

Case history tracking involves recording structured events like substantive, risk, and stakeholder updates into a managed matter history file. It requires validating the matter exists in the portfolio log and confirming settlement and materiality review gates before applying changes.

Can I update legal holds and exposure risk without unmanaged changes to the portfolio log?

Yes, you can update legal holds, exposure, and risk information by appending a dated event to the matter history. The system presents proposed history and YAML changes for confirmation before writing, ensuring all updates are documented and audit-ready.

How do I record a court order that changes litigation posture and deadlines?

Record a court order by appending the event to the matter history file as a procedural update. You then update the corresponding portfolio log fields for deadlines and status, ensuring the materiality reassessment gate is passed before confirming the changes.

Does matter management require confirmation before writing status and counsel updates?

Yes, matter management requires obtaining confirmation before writing any history or YAML changes. Proposed updates to status, counsel, owners, and deadlines are presented for review to ensure materiality and settlement gates are properly applied.

What are the limitations of appending administrative updates to a managed case history?

Administrative updates cannot be applied if the matter slug does not exist in the managed log. Additionally, all updates must pass settlement and materiality review gates, meaning unmanaged or undocumented changes to the portfolio log are blocked.