Menu

Individual skill

investigation-review-hub-remediation

0upvotes

Produce structured JSON remediation, production-readiness, retention, preservation, privilege, QC, and source-gap analyses from an Investigation Review Hub or similar matter review system. Use when a task provides a matter ID, answer template, and task-scoped hub access for subpoena, production, custodian-source, document-review, privilege-log, QC, retention, or remediation-action records.

experiments/codex_gpt5_5_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
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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 Remediation

## Core Workflow

1. Read the user prompt, task-local context payloads, and answer template before querying evidence. Treat the template as the output contract: required keys, item keys, enums, numeric precision, and ordering rules are binding.
2. Use only the task-provided hub/source-of-record access. Do not inspect local environment source files, database files, seed data, manifests, hidden notes, gold answers, or evaluation artifacts.
3. Scope every evidence query to the requested matter ID. Pull the schema if needed, then gather matter metadata, request categories, production stats, custodian sources, review documents, privilege entries, QC findings, retention events, and remediation actions.
4. Build the candidate issue universe from non-noise remediation actions first. Add direct non-action blockers only when the template asks for them, such as miscoded responsive documents, zero-production contradictions, missing required records, or explicit readiness metrics.
5. Exclude operational noise: records whose notes or action IDs say routine, noise, ordinary variance, corrected audit trail, resampling only, metadata-only cleanup, or not dispositive without source comparison, unless the prompt specifically asks for those records.
6. Emit one JSON object only. Do not include narrative, citations, schema commentary, or fields not requested by the answer template.

## Evidence Selection

Prefer stable hub record IDs as anchors:
Back to top