legal-hold

To draft a legal hold notice, this Skill generates a DOCX file containing custodian scope, date range, and systems details while enforcing house-style template norms. It requires loading matter context and a CLAUDE house-style file to ensure compliance before outputting the document.

Refreshing a litigation hold involves capturing scope or custodian changes to produce a new versioned DOCX notice. This action updates the last_refresh and next_refresh dates in the tracking log, and specifically flags any departed custodians for required preservation action.

Releasing a legal hold requires drafting a release notice DOCX and setting the released date in the log. The Skill enforces an unbypassable gate that prevents releasing without an existing log row, ensuring the action is confirmed and user-reviewed before restoring normal retention posture.

Yes, you can generate a portfolio-wide status report by running the Skill in a no-slug portfolio status mode. This mode is driven by the legal hold log, producing a comprehensive view of all active and overdue holds across your matters without needing a specific matter slug.

Yes, the workflow enforces an unbypassable gate that prevents issuing or releasing a hold without an existing log row. You must load matter context and ensure the _log.yaml tracking data is present before proceeding with any matter-scoped issuance or release actions.

A key limitation is the unbypassable gate preventing any issuance or release actions without an existing _log.yaml row. Additionally, the workflow requires loading a specific CLAUDE house-style file for template and privilege norms, making it incompatible with environments lacking these dependencies.