What problem does it solve? Keeping a litigation portfolio current requires disciplined, structured logging of every development. This Skill removes the friction of manually updating matter history files and the central matter log, ensuring status changes, risk re-assessments, deadline shifts, and settlement activity are captured consistently without freeform drift. ## Core Features & Use Cases - Structured Event Logging: Appends dated, categorized entries (procedural, discovery, substantive, strategy, risk, stakeholder, administrative) to a matter's history.md file. - Log Synchronization: Updates the _log.yaml row with field changes such as status, stage, risk, materiality, exposure range, and next deadline, always showing a diff before writing. - Compliance Gates: Enforces a conflicts-check gate requiring prior matter intake, a settlement-acceptance gate for non-lawyer users, and explicit materiality re-check prompts for triggering events. - Use Case: After receiving a settlement offer on an active matter, run the update to log the event, reclassify materiality, revise the exposure range, and record the reasoning in the matter history. ## Quick Start Ask the assistant to log an update on a matter by providing the matter slug and a brief description of the event, for example to record a new court order received today.
