{"id":17276,"plugin_id":"plugins_6a75dc82c0fc81919985d8f2dc208355","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:04.979Z","digest":"ebc1e52f732f6ea7f38f0f9075f743e181fee1f8cdeedd2b407997182716233c","against":null,"payload":{"description":"Plans defensible preservation and legal-hold measures for anticipated or active disputes, investigations, regulatory matters, or disclosure obligations. Use when identifying custodians and data sources, defining preservation scope, drafting hold notices, suspending deletion, monitoring compliance, documenting collection, or deciding when a hold may be narrowed or released.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":278}],"name":"legal-hold-planner","skill_md_contents":"---\nname: legal-hold-planner\ndescription: >-\n  Plans defensible preservation and legal-hold measures for anticipated or active\n  disputes, investigations, regulatory matters, or disclosure obligations. Use\n  when identifying custodians and data sources, defining preservation scope,\n  drafting hold notices, suspending deletion, monitoring compliance, documenting\n  collection, or deciding when a hold may be narrowed or released.\n---\n\n# Legal Hold Planner\n\nBuild a proportionate, auditable preservation plan without deciding that every\npotentially relevant item must be collected or produced.\n\n## Intake\n\nObtain the jurisdiction and forum, trigger event and date, claims or issues,\nparties, relevant period, known custodians, information systems, devices,\nthird-party repositories, routine deletion settings, existing holds, applicable\norders or protocols, responsible legal and IT personnel, and any cross-border,\nemployment, privacy, secrecy, privilege, or regulatory constraints.\n\nTreat the preservation trigger, governing duties, scope, and release standard as\njurisdiction-specific. If an immediate deletion risk exists, lead with interim\nsteps that preserve material without altering or over-collecting it.\n\n## Method\n\n1. State the event that may trigger preservation, the decision owner, the date\n   the duty may have arisen, and every legal or factual uncertainty.\n2. Translate the live issues into a preservation scope covering subjects, date\n   ranges, people, organisations, systems, locations, file types, communications,\n   structured data, physical records, and ephemeral or automatically deleted data.\n3. Build a custodian-and-source map. Distinguish possession, custody, control,\n   technical access, ownership, and third-party control rather than treating them\n   as interchangeable.\n4. Identify routine deletion, rotation, overwriting, device replacement, account\n   closure, auto-delete, backup expiry, and business processes that require a\n   documented suspension or exception.\n5. Draft clear notices stating purpose, scope, examples, prohibited actions,\n   acknowledgement, questions, confidentiality, update duties, and contact point.\n   Do not disclose privileged strategy unnecessarily.\n6. Define acknowledgement, reminder, interview, escalation, departure, new-\n   custodian, system-change, and compliance-check procedures with owners and dates.\n7. Preserve provenance and integrity during collection. Record source, custodian,\n   method, operator, date, time zone, filters, exceptions, hashes where suitable,\n   chain of custody, and any transformation.\n8. Reassess scope after pleadings, orders, interviews, settlements, or new facts.\n   Record every expansion, narrowing, and release decision and its authority.\n9. Plan release only after counsel confirms that relevant duties, appeals,\n   investigations, contractual holds, and overlapping matters have ended.\n\n## Output\n\nProvide a trigger memorandum, issue-to-scope map, custodian-and-source register,\ndeletion-risk table, hold notice, acknowledgement and reminder plan, collection\nand exception log, compliance dashboard, reassessment schedule, and release\nchecklist. Mark assumptions and unverified legal propositions conspicuously.\n\n## Guardrails\n\nDo not delete, alter, conceal, backdate, or selectively preserve evidence. Do not\npromise that a hold creates privilege, suspend systems without authorised IT and\nbusiness review, or collect entire accounts merely because preservation is broad.\nEscalate suspected spoliation, inaccessible encrypted data, departed custodians,\npersonal devices, sanctions exposure, or conflicts between preservation and law.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}