legal-hold

To issue a litigation legal hold and prevent spoliation risk, the skill drafts a notice to .docx, designates custodians, and updates the matter log. It manages the full lifecycle, appending audit trails and scheduling refresh deadlines automatically.

Drafting and refreshing legal hold notices across a matter portfolio requires applying matter context to generate .docx outputs and updating the log. The skill reaffirms scope and custodians on a cadence, appending audit trails to history files.

Yes, you can generate a portfolio-wide legal hold status report. The skill reads matter workspace context and log fields like issued, last_refresh, next_refresh, and released dates to produce comprehensive compliance tracking reports.

The best way to release a legal hold at matter resolution is to close the hold and record the release date. This skill enforces the conflicts gate via the matter log row and updates the history.md file with the final disposition.

Yes, legal hold compliance tracking requires updating a matter log. The skill writes issued, last_refresh, next_refresh, and released fields to `_log.yaml` and appends an audit trail to `history.md` to maintain defensible governance.

You need to refresh custodian management for a litigation hold on a regular cadence before the next_refresh deadline. This skill reaffirms scope and custodians to prevent spoliation risk and drafts updated legal hold notices as needed.