跳到正文
cccskills
免费在 GitHub 公开

disputes-and-legal-holds

Organize an operational response to a dispute: identify when records may need preservation, scope a written legal hold, and suspend relevant deletion systems. Track counsel, costs, privilege, and settlement considerations with legal counsel guiding strategy.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight.

实测评分 未实测

查看安装方法

适用场景

  • Responding to a demand letter
  • Identifying custodians and systems for a legal hold
  • Stopping automatic deletion of relevant records
  • Comparing settlement with the cost of continuing

包含的文件(2)

  • SKILL.md4.4 KB
  • references/sources.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Disputes and legal holds

The decisions that determine how a dispute goes are made in the first week, usually by people who do not know a dispute has started.

This structures the operational response. Procedural obligations and their deadlines vary by jurisdiction and forum — get counsel engaged early, and let them drive strategy.

Preservation attaches earlier than most people expect

The obligation to preserve begins when litigation is reasonably anticipated — which can be a demand letter, a threat made in a meeting, a regulator's inquiry, or an internal complaint serious enough that a claim is foreseeable. It does not wait for a filing.

Destruction after that point is treated far more seriously than the underlying dispute. Routine automatic deletion continuing through a hold is the common version, and "it was our normal policy" is not the defense people assume.

Issue the hold in writing, and make it reach the systems

A hold has two halves and organizations routinely do only the first.

  • Notify the people. Written, naming the matter in general terms, describing the categories of material to preserve, instructing recipients not to delete and not to discuss, and requiring acknowledgment. Identify custodians by what they touched, not by seniority.
  • Suspend the machinery. Automatic deletion runs on schedules nobody remembers setting: mail retention, chat history expiry, ticket archival, log rotation, backup rotation, CRM purges, device wipe on offboarding. Each needs an explicit suspension for the affected scope.

The systems half is where holds fail, because the notice goes out and everyone assumes it was sufficient. Keep a list of every system with an automatic deletion schedule so that the question is answerable in an afternoon rather than a fortnight.

Maintain the hold as a live thing

Re-notify periodically, add custodians as the matter develops, and cover departures — an employee leaving under a hold means their mailbox, files and device do not follow the standard offboarding path. Release the hold in writing when counsel says so, and only then.

Privilege is easy to lose and cannot be recovered

Privilege protects legal advice, not facts and not business decisions dressed as legal ones. Copying a lawyer onto a business discussion does not make it privileged; forwarding privileged advice widely inside the organization can waive it.

Where an investigation is being run for the purpose of legal advice, structure it that way from the start — directed by counsel, marked, and circulated narrowly. Retrofitting privilege afterward generally fails.

Manage counsel and cost deliberately

Agree scope, staffing, rates and a budget with checkpoints before work starts, and require early written assessment of the realistic range of outcomes. Discovery is usually the largest cost and the most controllable one — narrowing custodians and date ranges early matters more than any hourly rate negotiation.

Decide about settlement on expected cost, not on principle

Compare the realistic range of outcomes, weighted, against the full cost of continuing: fees, management time, disruption, disclosure risk, and the effect on other matters. Management time is the cost most consistently omitted and is often the largest.

Consider what a settlement signals to other potential claimants, and get releases that are broad enough to actually end it.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Wait for a filing before preserving.
  • Send a hold notice without suspending the automatic deletion it depends on.
  • Offboard someone under a hold through the standard process.
  • Assume copying counsel on a message makes it privileged.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Design and review access so people and services have appropriate permissions. Use it to plan roles, audit accounts, reduce always-on admin rights, manage credentials, handle departures, and improve sign-in with single sign-on or multi-factor authentication.

中文简介正在准备中。当前显示英语简介。

  • Reviewing who can access each system
  • Planning role based permissions
  • Removing access during offboarding
cbrock84/headcount20852026年10月19日 更新

Plan account-based marketing for a defined set of companies. Assess whether the economics fit, prioritize accounts, map the people involved in buying, coordinate outreach across sales and marketing, and track account movement through the pipeline.

中文简介正在准备中。当前显示英语简介。

  • Assess whether account-based marketing fits the business
  • Build and prioritize a target account list
  • Map buying roles within target companies
cbrock84/headcount20852026年10月19日 更新

Improve the path from signup to a new user’s first meaningful result. Define the action that signals real value, refine signup and onboarding, and diagnose where people drop off so more accounts become active users sooner.

中文简介正在准备中。当前显示英语简介。

  • Designing or fixing signup and onboarding
  • Finding why signups do not become active users
  • Reducing time to a first meaningful result
cbrock84/headcount20852026年10月19日 更新

Design a repository’s multi-agent structure by assigning exclusive file areas, defining builder and reviewer roles, and checking ownership rules with a CI script. Use it to divide work, prevent overlapping edits, and decide whether another agent is needed.

中文简介正在准备中。当前显示英语简介。

  • Dividing repository work among agents
  • Defining agent roles and file ownership
  • Auditing overlapping agent responsibilities
cbrock84/headcount20852026年10月19日 更新

Use this skill to define an AI system’s intended use, evaluate its errors across user groups, plan monitoring and meaningful human review, and document its limits. It supports deployment and retirement decisions, especially when AI could affect consequential outcomes for people.

中文简介正在准备中。当前显示英语简介。

  • Set evaluation criteria before deployment
  • Investigate model behavior drift
  • Plan monitoring and human review
cbrock84/headcount20852026年10月19日 更新

Use this skill to analyze markets, map competitors, assess trends, and compare strategic options such as market entry or build versus buy. It produces a cited research brief that separates established facts from inferences and estimates, states confidence, and connects findings to a decision.

中文简介正在准备中。当前显示英语简介。

  • Sizing a market or analyzing an industry
  • Mapping competitors and buyer differences
  • Comparing market entry or build versus buy
cbrock84/headcount20852026年10月19日 更新

查看 cbrock84 的全部技能

报告此技能的问题