legal-hold

Manage Russian legal document preservation orders across hold, refresh, and release workflows.

17|4|Updated May 25, 2026
One-click install
npx skills add https://github.com/AlsKozlov/ru-legal --skill legal-hold-alskozlov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legal-hold
Source: https://github.com/AlsKozlov/ru-legal/tree/main/packs/litigation/skills/legal-hold
Command: npx skills add https://github.com/AlsKozlov/ru-legal --skill legal-hold-alskozlov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In the Russian legal system, companies face significant risk of spoliation (destruction of relevant evidence) claims if they fail to preserve documents related to potential or ongoing litigation, regulatory investigations, or pre-litigation claims. Unlike the US, Russia has no standardized legal hold framework, leaving organizations to navigate conflicting requirements between procedural law (e.g., APK Article 72 for pre-litigation evidence preservation), personal data protection rules (152-FZ), and internal document retention policies without clear, structured guidance. Non-legal staff may also issue or release preservation orders without proper authorization, creating additional legal liability.

Core Features & Use Cases

  • End-to-End Legal Hold Workflows: Structured, step-by-step guidance for issuing, refreshing, releasing, and checking the status of internal document preservation orders aligned with Russian law.
  • Built-In Governance Guardrails: Mandatory non-lawyer authorization checks for hold issuance and release, requiring sign-off from a general counsel, lead attorney, or DPO for personal data-related holds to prevent unauthorized legal action.
  • Regulatory Alignment: Explicit integration of key Russian legal requirements, including APK Article 72 pre-litigation preservation rules, 152-FZ personal data handling obligations during holds, and standard post-release document retention timelines (e.g., 5 years for accounting records per 402-FZ).
  • Use Case: If your company receives a pre-litigation claim from a counterparty, use this skill to issue a formal preservation order to all relevant custodians, track hold status, and release the order only after the matter is fully resolved to avoid premature document deletion.

Quick Start

Use the legal-hold skill to issue a preservation order for the Acme counterparty claim matter, specifying all relevant custodians, document categories, and the trigger event date.

Frequently Asked Questions about legal-hold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I issue a legal hold for litigation in Russia to prevent spoliation?

A legal hold under Russian law requires issuing a formal preservation order to custodians, tracking hold status, and releasing it only after the matter resolves. It aligns with APK Article 72 for pre-litigation preservation and 152-FZ for personal data protection.

What is pre-litigation evidence preservation under APK Article 72?

Pre-litigation evidence preservation under APK Article 72 is a Russian procedural mechanism to secure documents before formal disputes escalate. It is triggered by counterparty claims, subpoenas, or regulator requests to prevent spoliation and ensure evidence remains available.

Can non-lawyer staff release a document preservation order in Russian companies?

No, non-lawyer staff cannot release a document preservation order without proper authorization. Governance guardrails mandate sign-off from a general counsel, lead attorney, or DPO for personal data-related holds to prevent unauthorized legal action and mitigate corporate liability.

How does 152-FZ affect personal data handling during a legal hold?

The 152-FZ personal data protection rules impose specific obligations during legal holds, restricting how personal data is processed and preserved. The hold workflow integrates these requirements to ensure compliance while securing evidence for litigation or regulatory matters.

What is the retention period for accounting records after releasing a legal hold under 402-FZ?

After releasing a legal hold, standard document retention timelines apply, such as a 5-year retention period for accounting records per 402-FZ. The release workflow ensures holds are lifted only after matter resolution while maintaining statutory retention compliance.

When should I use a structured legal hold workflow instead of informal document preservation?

A structured legal hold workflow is necessary when facing pre-litigation claims, regulatory investigations, or ongoing disputes in Russia. Informal preservation risks spoliation claims, conflicts between procedural law and data protection rules, and unauthorized hold releases by non-legal staff.