matter-update

Append dated events to matter history and update _log.yaml fields.

Updated May 28, 2026
One-click install
npx skills add https://github.com/gtgspot/clegal --skill matter-update-gtgspot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: matter-update
Source: https://github.com/gtgspot/clegal/tree/main/litigation-legal/skills/matter-update
Command: npx skills add https://github.com/gtgspot/clegal --skill matter-update-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps matter records accurate by recording updates, changes in status, risk assessments, deadlines, and authority decisions in a centralized history and log.

Core Features & Use Cases

  • Append a dated event to a matter's history file at matters/[slug]/history.md.
  • Update the matter log (_log.yaml) with the date and any field changes (status, stage, risk, materiality, deadlines, ownership).
  • Validate matter existence in the log before updating to prevent unmanaged workspaces.
  • Provide a guided, structured input flow to capture event type, date, summary, and relevant field changes.

Quick Start

Run the matter-update flow with a slug and a brief event description to append the update to the matter history and refresh the log.

Frequently Asked Questions about matter-update

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

FAQPage Schema
How do I append an event to a matter's history file and refresh the matter log?▼

To append an event to matter history and refresh the log, provide the matter slug, event type, date, and summary. The workflow writes to history.md and updates _log.yaml with the last_updated timestamp and any field changes.

What is the best way to keep litigation matter records accurate with status changes and deadlines?▼

Keeping litigation matter records accurate requires logging updates like status changes and deadlines in a centralized history file. This workflow appends dated events to history.md and applies selective field changes to the matter log.

Can I update matter log fields like risk, stage, and ownership in bulk?▼

You can update matter log fields including status, stage, risk, materiality, deadlines, and ownership. The guided input flow captures these selective field changes and applies them to _log.yaml alongside the history event.

Does matter-update require a conflicts check before recording compliance history?▼

Yes, matter-update enforces a conflicts gate before recording compliance history. This validation ensures matter updates only proceed when conflicts are cleared, maintaining record integrity across the workspace.

What happens if I try to log an update for a matter slug that doesn't exist in the workspace?▼

If the matter slug doesn't exist in the workspace, the update fails. The workflow validates matter existence in _log.yaml before updating to prevent unmanaged workspaces from receiving history entries or field changes.