matter-update

Append dated event records to case history and synchronize matter YAML logs.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill matter-update-zhou210712
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: matter-update
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/litigation-legal/skills/matter-update
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill matter-update-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps legal teams record new litigation events in a consistent, dated way and keep the matter’s history and YAML log up to date so the case record remains usable for ongoing risk review and workflow continuity.

Core Features & Use Cases

  • Append dated event entries to case history: Adds a new, properly formatted entry to the case’s history.md with event type, summary, and optional file associations.
  • Refresh the centralized _log.yaml: Updates last_updated and applies any provided field changes such as status, stage, risk, materiality, deadlines, owners, and legal hold.
  • Enforce guardrails before writing: Refuses to append history if the case code is not present in matters/_log.yaml, routing the user to matter intake first; additionally, requires a stricter gate when the update is an “accept settlement” action.

Use Case: You learn that a court scheduled a new hearing next month and you also received a document that may affect exposure—use this Skill to record the hearing scheduling and update the relevant risk or next-deadline fields in one structured pass.

Quick Start

Run /litigation-legal:matter-update and provide the case code plus an event type, date (or leave blank for today), and a concise summary of what changed.

Frequently Asked Questions about matter-update

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

FAQPage Schema
How do I append a new hearing date to litigation case history?

To append a hearing date to litigation case history, provide the case code, event type, date, and summary. The Skill formats the entry into the case's history.md and synchronizes updated deadlines in the matter YAML log.

What happens if I try to update a case code that is not in the log?

If the case code is missing from matters/_log.yaml, the history update is refused and you are routed to matter intake first. The Skill enforces this guardrail to ensure case records remain consistent.

Can I update risk assessment and materiality fields during a litigation event update?

Yes, you can update risk and materiality fields during a litigation event update by providing the new values. The Skill applies these changes to the centralized _log.yaml alongside appending the dated history entry.

Does accepting a settlement require a special validation gate?

Accepting a settlement requires a stricter validation gate before writing to the case history. This role-based safety gate ensures authorization before finalizing settlement acceptance entries in the litigation matter log.

How do I record a substantive development and update legal hold status simultaneously?

Record a substantive development and update legal hold status simultaneously by running the update with the case code, event summary, and changed legal hold value. The Skill appends the event to history.md and syncs the _log.yaml fields.

What is the best way to track litigation strategy changes in a centralized YAML log?

The best way to track litigation strategy changes in a centralized YAML log is using a structured matter update that appends dated event records to history.md and synchronizes supported fields like stage, owners, and risk in _log.yaml.