Guides drafting of a formal response to a regulatory compliance order by organizing the analysis count-by-count, evaluating available defenses and mitigation themes, and proposing a compliance schedule with achievable milestones.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill draft-response-to-epa-compliance-order --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Response To Epa Compliance Order?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-draft-response-to-epa-compliance-order)More formats (shields.io, HTML) on the badges page.
---
name: draft-response-to-epa-compliance-order
task_id: environmental-esg/draft-response-to-epa-compliance-order
description: Guides drafting of a formal response to a regulatory compliance order by organizing the analysis count-by-count, evaluating available defenses and mitigation themes, and proposing a compliance schedule with achievable milestones.
activates_for: [planner, solver, checker]
---
# Skill: Draft Response to EPA RCRA Compliance Order
## 1. Subject-matter triage
- Confirm the order is an administrative enforcement response under RCRA and identify the operative statutory, regulatory, and order provisions before drafting.
- Separate conceded violations from contested allegations, and separate merits defenses from mitigation-only arguments.
- Determine whether the response should include factual admissions, proposed corrective actions, a settlement posture, and a request for penalty adjustment or payment terms.
## 2. Failure modes the skill is correcting
- Baseline drafts a global narrative response without organizing the analysis count-by-count to address each alleged violation separately.
- Baseline omits defenses commonly available in enforcement responses, such as emergency response, force majeure, or good-faith compliance, that are supported by facility records.
- Baseline does not use available environmental, health, and safety records, compliance history, and inspection documents to substantiate factual defenses for each contested count.
- Baseline proposes a compliance schedule without assessing technical feasibility of each milestone based on available operational and construction data.
- Baseline states legal conclusions without tying them to the controlling RCRA provision, implementing regulation, or penalty authority.
- Baseline discusses alleged violations without distinguishing the inspection period from post-inspection corrective action and resulting mitigation.
## 3. Legal frameworks / domain conventions that apply
- Identify the order authority, the alleged RCRA obligations, and the penalty or settlement framework implicated by the agency action; cite the controlling statute, regulation, or order provision for each legal proposition.
- Common RCRA compliance topics include generator status, accumulation limits and timing, container management, labeling, inspection, manifesting, land disposal restrictions, and recordkeeping.
- Penalty analysis typically turns on gravity, economic benefit, history of noncompliance, good-faith efforts, ability to pay, and timely corrective action; use the applicable agency penalty policy or comparable enforcement factors.
- Defenses and mitigation themes commonly include factual nonoccurrence, ambiguity in the cited requirement, prompt correction, emergency conditions, force majeure, and lack of economic benefit; support each with the governing rule or policy.
- If corrective action, reporting, or ongoing operational controls are implicated, align any proposed schedule with the applicable regulatory process and permit or order obligations.
- Use only authority-supported defenses; do not overstate equitable arguments where the cited rule requires a specific notice, documentation, or timing showing.
## 4. Analytical scaffolds
- Enumerate each count first, then analyze each count in the same sequence as the order.
- For each count, identify:
- the cited regulatory requirement;
- the alleged factual condition;
- the relevant time period;
- whether the allegation is denied, admitted, or partially admitted;
- the records that support the response.
- For each contested count, test the agency’s theory against facility records, manifests, inspection logs, training records, photographs, correspondence, and corrective-action documents.
- For each admitted or partially admitted count, state the corrective action already taken, the remaining work, and the legal or operational reason the violation should be treated as mitigated.
- For force majeure or emergency-based defenses, identify the triggering event, the duration, the specific causal chain to the alleged violation, and the documentation and notice showing compliance with the applicable requirement.
- For penalty reduction, address each relevant factor separately and connect the facts to the requested adjustment.
- For compliance scheduling, break the work into milestones that are technically realistic, sequenced, and tied to actual procurement, construction, shutdown, testing, training, or certification needs.
- Draft the response as a formal administrative letter that includes count-by-count responses, penalty mitigation, a proposed schedule, and a settlement posture or reservation of rights as appropriate.
## 5. Vertical / structural / temporal relationships
- Compare the inspection date, alleged violation period, and response date to show whether the cited condition existed when the agency says it did.
- Distinguish pre-order conditions from post-inspection corrective action; later remediation may mitigate penalty even if it does not erase a past violation.
- If multiple sites, waste streams, or operating units are involved, keep each one separate so that facts, defenses, and corrective actions do not bleed across counts.
- If a penalty component is said to reflect delayed compliance, address the timing of the alleged delay and any intervening efforts that reduced or eliminated environmental risk.
- If the order references ongoing obligations, ensure the proposed schedule does not conflict with deadlines already imposed by law, permit, consent process, or prior agency correspondence.
## 6. Output structure conventions
- Write the deliverable as a formal business letter or administrative response, with date, recipient, subject line, order reference, and clear closing request.
- Use a count-by-count body in the same order as the order; for each count, include the allegation, response, applicable authority, supporting facts, and current status.
- Include a separate penalty section that requests reduction, modification, or deferral using the recognized penalty factors and supporting facts.
- Include a compliance schedule section with a milestone table or list that gives specific tasks, sequencing, and target dates.
- Include a settlement or resolution paragraph that preserves appropriate rights while inviting resolution on defined terms.
- Keep the tone professional, factual, and regulatory; avoid advocacy language that is unsupported by the record.
- If the source materials identify a required deadline or response window, state compliance with it expressly.
- Deliver the primary file named `compliance-order-response-letter.docx` and ensure it contains the operative response letter, not merely an outline or summary.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!