matter-update

To append a litigation matter history log entry, provide the matter slug, event type, date, and summary. The Skill validates the slug against `_log.yaml` and writes a structured, dated entry to `history.md`.

Matter log synchronization works by updating `_log.yaml` metadata to set `last_updated` and apply prompted field changes for risk, materiality, status, and deadlines whenever a new event is appended to the matter's history log.

Yes, you can track deadline shifts and settlement authority changes. The Skill includes guided prompts for relevant field updates and an optional settlement-acceptance guardrail to ensure authority changes are logged consistently.

You need a workspace containing a `_log.yaml` file for matter slug validation and a `history.md` file. The Skill enforces a conflicts gate to ensure history is only appended for matters that already exist in `_log.yaml`.

If a matter slug does not exist in `_log.yaml`, the conflicts gate blocks the update. This prevents stale or unauthorized litigation records from being created, ensuring history is only appended for validated matters.

The best way to log procedural and substantive developments is to submit a brief summary with the event type and date. The Skill structures this into a dated history entry and synchronizes the matter's YAML log metadata automatically.