# Compare Remedial Action Work Plan Against Record Of Decision Requirements > Guides compliance gap analysis of a remedial action work plan against its governing decision document by systematically comparing each work plan element against the remedy selection rationale, performance standards, and institutional controls the decision document requires. - Skill: `finchipaiorg/compare-remedial-action-work-plan-against-record-of-decision` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/compare-remedial-action-work-plan-against-record-of-decision` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/compare-remedial-action-work-plan-against-record-of-decision/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/compare-remedial-action-work-plan-against-record-of-decision --- # Skill: Compare Remedial Action Work Plan Against Record of Decision Requirements — Compliance Gap Analysis Memorandum ## 2. Failure modes the skill is correcting - Describes the work plan in isolation without testing each provision against the governing remedy document, consent order milestones, pre-design findings, and community input. - Treats the decision document as a general backdrop rather than a source of specific cleanup levels, remedial action objectives, land-use controls, monitoring obligations, and approval conditions. - Conflates decree-based schedule obligations with substantive remedy requirements and misses where one can be met while the other is not. - Fails to account for post-decision investigation data that may show the work plan is designed around outdated site assumptions. - Omits the public-facing record: community comments and correspondence are not integrated as a separate compliance and risk dimension. - States a gap without anchoring it to the governing language, the related source document, and the downstream regulatory or operational consequence. ## 3. Legal frameworks / domain conventions that apply - CERCLA and the remedy-selection record: the decision document controls the remedial action objectives, cleanup criteria, institutional controls, and implementation expectations. - RD/RA execution practice: the work plan must show how the proposed design, sequencing, monitoring, health and safety, and construction methods will achieve the selected remedy. - Consent decree or equivalent enforcement instrument: schedule, reporting, submittal, and approval milestones must be analyzed separately from substantive remedy compliance. - Pre-design investigation practice: later sampling, delineation, or engineering data can confirm, refine, or materially depart from assumptions embedded in the decision document. - Institutional controls and long-term stewardship: use restrictions, notices, easements, operation-and-maintenance measures, and verification obligations should be checked for completeness and durability. - Community involvement record: public comments, meeting notes, and letters are part of the administrative record and should be addressed as a distinct category of issue and response. - Governing authority citations: when stating a legal proposition, identify the controlling statute, regulation, decree provision, or decision-document requirement by name and section or comparable pinpoint reference. ## 4. Analytical scaffolds - Build a requirement-by-requirement inventory from the decision document, then map each item to the work plan provision that purports to satisfy it. - Test each mapped item for four questions: does the work plan address the requirement, does it do so in a technically credible way, does it do so on the required timeline, and does it preserve any required follow-on controls? - Separate substantive remedy gaps from sequencing, deliverable, and approval-path gaps; do not collapse them into a single conclusion. - Where the pre-design record shows changed site conditions, compare the current condition against the assumption embedded in the decision document and state whether the work plan needs adjustment, clarification, or amendment consideration. - Where the remedy is phased, evaluate each phase on its own terms and also check whether the current phase depends on future phases for compliance, performance, or risk containment. - For each community concern, identify whether the work plan addresses it directly, indirectly, or not at all; if addressed, identify the specific mechanism or commitment. - For every gap entry, state: the governing requirement, the responsive or missing work-plan language, the mismatch, the consequence of the mismatch, and a concrete corrective action. - When the source set contains multiple media, operable units, exposure pathways, or work phases, enumerate them first and analyze each one separately rather than using a single representative pass. ## 5. Vertical / structural / temporal relationships - Pre-decision to post-decision to work-plan timeline: distinguish what the decision document assumed, what later investigation changed, and what the work plan currently proposes. - Regulatory to contractual layering: treat substantive remedy requirements, decree deadlines, and approval conditions as related but distinct constraints. - Phase-to-phase dependency: if current work depends on later construction, future institutional controls, or deferred sampling, identify the dependency and its compliance risk. - Community-record to implementation link: if comments raise design, nuisance, access, or transparency concerns, test whether the work plan includes an implementation response, not merely a narrative acknowledgment. - Current-conditions override: where updated data undermines an assumption in the decision document, flag the need for technical reconciliation and, if warranted, formal modification pathways. ## 6. Output structure conventions - Draft the result as a compliance gap analysis memorandum, not as a simple summary. - Use conventional memo sections such as: Executive Summary; Governing Requirements and Source Set; Requirement-to-Work-Plan Matrix; Detailed Gap Analysis; Community Concerns and Responses; Recommendations. - Include a defined ordinal severity scale at the outset and apply it uniformly to each gap entry. - For each gap entry, include: severity, the governing requirement, the corresponding work-plan provision or omission, the source document cross-reference, the consequence, and the recommended fix. - In the matrix, preserve a one-row-per-requirement structure so the reader can see coverage, partial coverage, or omission at a glance. - Do not merge multiple distinct requirements into one row if they arise from different governing sources or distinct phases. - End with an explicit Recommended Actions section that assigns each action to a responsible role and ties it to the relevant milestone, submittal deadline, or regulatory trigger. - Use the filename specified in the task instructions exactly: `gap-analysis-memorandum.docx`.