Guides drafting of a formal response to an agency notice of violation by organizing defenses by allegation, distinguishing defensible from conceded allegations, proposing a supplemental environmental project where appropriate, and requesting an informal conference.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill draft-response-letter-to-agency-notice --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Response Letter To Agency Notice?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-draft-response-letter-to-agency-notice)More formats (shields.io, HTML) on the badges page.
---
name: draft-response-letter-to-agency-notice
task_id: environmental-esg/draft-response-letter-to-agency-notice
description: Guides drafting of a formal response to an agency notice of violation by organizing defenses by allegation, distinguishing defensible from conceded allegations, proposing a supplemental environmental project where appropriate, and requesting an informal conference.
activates_for: [planner, solver, checker]
---
# Skill: Draft Response Letter to Agency Notice of Violation
## 1. Subject-matter triage
- Treat the notice as an allegation-by-allegation enforcement response, not a general narrative.
- Identify the governing agency program, the cited rule provisions, the compliance dates, and the response deadline before drafting.
- Separate alleged monitoring failures, emissions exceedances, recordkeeping issues, and operational incidents into distinct response buckets.
- If the notice covers multiple time periods or multiple incident types, enumerate them first and respond to each in sequence.
## 2. Failure modes the skill is correcting
- Drafts respond globally instead of addressing each alleged violation individually.
- Drafts either deny everything or concede everything, rather than making measured, evidence-based distinctions.
- Drafts omit a penalty-mitigation discussion even where the record supports good-faith efforts, prompt correction, or limited harm.
- Drafts fail to ask for an informal conference or to preserve negotiation posture.
- Drafts ignore available facility records that can support factual defenses, narrow acknowledgments, or mitigation.
- Drafts state conclusions without tying them to the cited regulatory standard or evidence in the record.
## 3. Legal frameworks / domain conventions that apply
- State environmental enforcement procedure governs the response format, settlement posture, and informal conference rights.
- The agency’s cited rule, permit condition, or order provision controls the substantive compliance standard; quote or paraphrase it carefully without overclaiming.
- Penalty discussion should track the program’s usual factors: severity, duration, culpability, cooperation, corrective action, history, and environmental impact.
- Supplemental environmental projects are assessed for nexus to the alleged conduct, environmental benefit, feasibility, and any program-specific credit rules.
- If the record supports an upset, malfunction, or force-majeure-style defense, use the applicable regulatory defense standard and its notice/documentation prerequisites.
- Where monitoring or operating data are relied on, match the correct averaging period, sampling window, and measurement method to the cited requirement.
- If the agency’s notice references prior inspections, prior notices, or prior corrective commitments, characterize that history accurately and only as supported by the source materials.
- Cite controlling authority for each legal proposition used in the letter, including the cited regulation, permit condition, statute, or rule-based procedure.
## 4. Analytical scaffolds
- Start by listing every alleged violation, each citation, and the agency’s factual basis.
- For each allegation, review the available facility data, inspection notes, logs, monitoring records, reports, and correspondence that relate to the cited period.
- Classify each allegation into one of three categories:
- defensible on the merits,
- partially defensible with mitigation,
- narrowly acknowledged with corrective-action framing.
- For defended allegations, state the governing standard, identify the operative facts, and explain why the evidence does not establish the alleged breach.
- For partially defensible allegations, concede only the narrow point that is supported while disputing scope, duration, causation, or characterization.
- For acknowledged allegations, avoid expansive admissions; pair the acknowledgment with immediate corrective action, root-cause review, and future-prevention language.
- If the notice involves an incident defense, check whether the source documents show timely notice, prompt response, and required documentation.
- Use penalty mitigation arguments only where supported by the record, and anchor them in the program’s recognized factors rather than general fairness rhetoric.
- If proposing a supplemental environmental project, select a project concept with a clear nexus to the cited concerns and describe its environmental benefit in concrete but non-quantified terms unless the source documents supply approved figures.
- Request an informal conference explicitly, identify the issues to be discussed, and preserve the client’s ability to pursue settlement or further administrative review.
- Keep the tone formal, cooperative, and non-adversarial while preserving contested positions.
## 5. Vertical / structural / temporal relationships
- Order the response to track the notice: cite each allegation, then respond to it immediately.
- Distinguish what occurred before the notice, what was corrected after the notice, and what remains in progress.
- Tie any corrective action to the earliest documented response date available in the source materials.
- If the record contains multiple facilities, units, or operational areas, keep their facts separated unless the notice expressly aggregates them.
- Where timing matters, match the cited compliance window rather than relying on a broader facility history.
## 6. Output structure conventions
- Draft as a formal business letter addressed to the agency contact identified in the notice.
- Open with the notice reference, response purpose, and an express statement that the response is timely or submitted within the stated deadline.
- Include an allegation-by-allegation section that tracks the notice’s order and states for each item:
- the allegation,
- the response position,
- the evidence or authority supporting that position,
- and any corrective action or mitigation point.
- Include a separate section for penalty mitigation and settlement considerations, if supported by the record.
- Include a separate paragraph proposing a supplemental environmental project, if appropriate, described at a program-appropriate level of specificity.
- Include a separate and explicit request for an informal conference.
- End with a concise reservation-of-rights or no-waiver statement if appropriate to the posture.
- Use professional letter format, with subject line, date, and signature block consistent with the client and agency.
- Ensure the deliverable is the final .docx response letter itself; do not substitute an outline or memo.
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!