# Identify Issues In Expert Remediation Report > Guides preparation of a prioritized vulnerability memorandum by identifying methodological, data, and credibility weaknesses in an expert remediation report for a cost-recovery defense. - Skill: `finchipaiorg/identify-issues-in-expert-remediation-report` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/identify-issues-in-expert-remediation-report` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/identify-issues-in-expert-remediation-report/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/identify-issues-in-expert-remediation-report --- # Skill: Identify Issues in EPA Expert Remediation Report for CERCLA Cost Recovery Defense ## 1. Subject-matter triage - Treat the task as a comparative issue-spotting exercise across the expert feasibility report, the RI data, the complaint, the transmittal, the expert CV, and defense counsel’s preliminary notes. - Start with the defense expert’s notes to identify the most useful rebuttal themes, then test those themes against the source set. - If the source set includes multiple media, contaminants, operable units, alternatives, or time periods, enumerate them first and analyze each separately rather than using a single blended pass. - Keep the focus on vulnerabilities that can be turned into defense themes, impeachment points, or narrow fact disputes with record support. ## 2. Failure modes the skill is correcting - Reviewing the feasibility report in isolation instead of checking whether its factual premises track the RI data, complaint allegations, and transmittal materials. - Stopping at generic “methodology concerns” without isolating the exact assumption, data selection, calculation choice, or evaluative step that is attackable. - Missing where the report overstates certainty, assumes full-scale performance, or treats undeveloped technologies as proven without adequate support. - Failing to test cost estimates, contingency assumptions, and omitted categories against standard remediation costing conventions. - Ignoring the expert’s qualifications, experience fit, publication record, and prior testimony history as impeachment material. - Producing an undifferentiated critique rather than a ranked memo that separates decisive weaknesses from minor factual points. - Neglecting to convert each identified weakness into a concrete litigation use: rebuttal, cross-examination, or narrower evidentiary challenge. ## 3. Legal frameworks / domain conventions that apply - CERCLA cost recovery and remedial-response framing: evaluate whether the report supports response-cost recovery positions and remedy criticism under the applicable CERCLA framework. - Feasibility-study conventions: compare alternatives using the standard remedial-evaluation criteria for protectiveness, compliance with applicable requirements, long-term effectiveness, reduction of toxicity/mobility/volume, short-term effectiveness, implementability, cost, and acceptance factors where relevant. - Expert reliability standards: assess whether the report’s reasoning is testable, data-driven, transparent about assumptions, and consistent with accepted scientific or engineering practice; flag unsupported extrapolation and conclusory analysis. - Disclosure and foundation conventions: test whether the report identifies the factual basis, assumptions, data exclusions, and calculation steps needed to support its conclusions. - Cost-estimation conventions: test the basis for unit pricing, contingency, escalation, indirect costs, and completeness of cost categories. - Treatability and performance conventions: where a remedy depends on an emerging or unproven technology, require support from treatability, pilot, or comparable performance data before accepting assumed outcomes. - Expert impeachment conventions: evaluate fit between the witness’s background and the opinions offered, plus any prior testimony or publication material that weakens reliability or neutrality. ## 4. Analytical scaffolds - Read the defense expert notes first and use them to define likely attack lanes; do not overwrite them with a generic audit. - Build an issue inventory by source document: what the feasibility report says, what the RI data actually show, what the complaint alleges, what the transmittal frames as important, and what the CV reveals. - For each material conclusion, trace the chain from underlying data to the report’s stated conclusion; flag any break in that chain caused by unsupported selection, omission, extrapolation, or mismatch. - For each evaluation criterion, test whether the report gives a real comparative analysis or only a conclusory label. - For each cost item or remedy assumption, ask whether the report identifies the costing basis, the relevant inputs, and any omitted line items or double counts. - For each technology claim, ask whether the performance assumption is grounded in actual testing, field history, or just aspirational design intent. - For the CV, isolate domain mismatch, thin experience, stale experience, advocacy bias, and prior testimony themes that can support impeachment. - Rank each issue by how much it undermines the report’s core conclusion and how well it can be supported from the source set. ## 5. Vertical / structural / temporal relationships - Data-to-report chain: treat the RI tables as the factual foundation; if the report departs from them, note whether the departure is due to an error, an unstated assumption, or a selective read. - Allegation-to-remedy chain: use the complaint to understand which site conditions and remedy consequences matter most; focus on weaknesses tied to those disputed points. - Transmittal-to-analysis chain: if the transmittal narrows or frames the expert assignment, note any overreach beyond that mandate. - Timeline sensitivity: if the report depends on conditions, concentrations, costs, or regulatory status at different times, separate present facts from historical conditions and avoid collapsing them. - Document interaction: identify where one source document qualifies, limits, or contradicts another, and state the practical effect of that tension on the expert’s conclusion. ## 6. Output structure conventions - Produce a prioritized vulnerability memorandum, not a narrative summary. - Use a clear severity scale defined once at the top and apply it consistently to every issue entry. - Open with an executive summary listing the top vulnerabilities in descending order of importance. - Then present issue-by-issue analysis grouped by conventional categories: data/methodology issues, evaluation deficiencies, cost-estimation issues, technology-performance assumptions, and expert qualifications/credibility. - For each issue, include: the specific proposition in the expert report; the countervailing source material or governing convention; why the point is weak; the downstream consequence for the defense; and the recommended litigation use. - Make the issue entry self-contained by tying it to a concrete figure, threshold, time period, or comparable scale from the source set where available; cross-reference any interacting source document; and state the consequence for the client. - End with a Recommended Actions section that gives imperative next steps, assigns them to the responsible role drawn from the source set where possible, and ties each step to an immediate or milestone-based timing anchor. - Use ordinary legal memoranda conventions for headings and bullets; avoid reproducing any source-set-specific rubric labels. - Name the deliverable exactly as instructed: issue-identification-memo.docx.