matter-update

To log a litigation development, append a timestamped entry to the matter history and refresh the corresponding _log.yaml fields. This records procedural, disclosure, or substantive events safely by confirming the history entry and YAML diff before writing.

No, matter update requires the slug present in _log.yaml as an unbypassable conflict gate. If the slug is missing, the skill refuses to write, requiring an intake step first to ensure unmanaged matters are not updated silently.

Materiality and risk re-assessment changes are tracked by forcing explicit reclassification prompts for substantive developments and settlement activity. This ensures risk updates are deliberate and captured in the matter history log alongside the event metadata.

Yes, field-level changes to next_deadline, outside_counsel, status, stage, and risk are captured when logging strategy events. The skill shows the exact YAML diff for these log-field changes before writing them to the matter log.

Deadline tracking works by refreshing the next_deadline field in _log.yaml when recording administrative or pre-action events. The timestamped history entry and updated log fields are confirmed before any changes are written to the matter file.

Appending a dated event requires event metadata including type, date, summary, and relevant log-field changes. The skill applies this to procedural, stakeholder, or risk re-assessment events and confirms the resulting history entry and YAML diff before writing.