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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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.
A hold has two halves and organizations routinely do only the first.
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.
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 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.
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.
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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。