Individual skill

investigation-hub-production-gap-analysis

Produce a structured-JSON litigation e-discovery gap / production-readiness / remediation analysis for an investigation matter whose evidence lives in a read-only "Investigation Review Hub". Use when a task gives a matter_id, points at a review hub as the source of record, and asks for a JSON object conforming to a provided answer_template.json (critical findings, category statuses, retention/communication gaps, privilege corrections, top risks, metrics, prioritized actions, etc.). Covers subpoena/grand-jury/SEC/DOJ production reviews across custodian collection, preservation/retention loss, privilege logging, third-party waiver, and QC/responsiveness coding.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_017/reflect-3/reflect-3_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Investigation Review Hub — production gap analysis

These tasks share one shape: a legal team wants a normalized JSON assessment of
what is wrong with a rolling production for one matter. The prose, the client
name, and the output field names change; the underlying data model and the
reasoning do not. Solve it by pulling the matter's records from the hub,
separating the few **material** records from a large field of look‑alike
**distractors**, deriving exact counts, classifying each with domain rules, and
emitting JSON that conforms exactly to the task's `answer_template.json`.

## What the task hands you

- A **prompt** naming a `matter_id` and the deliverable.
- `input/payloads/answer_template.json` — the output contract: required top‑level
Back to top