# Draft Environmental

> Guides drafting of a formal public comment letter opposing reissuance of a draft NPDES permit by structuring legal and technical objections around the applicable permitting standards, anti-backsliding concerns, and water quality-based effluent limit adequacy.

- Skill: `finchipaiorg/draft-environmental` (Agent Skill)
- Install (CLI): `npx skillmds@latest add finchipaiorg/draft-environmental`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-environmental/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/draft-environmental

---


# Skill: Draft Public Comment Letter Opposing Proposed NPDES Permit Reissuance

## 1. Subject-matter triage
- Treat the assignment as a formal regulatory comment letter, not a general advocacy memo.
- Identify the permit action, the receiving water, the discharge source, the comment deadline, and the specific draft conditions being challenged before drafting.
- If the record contains multiple outfalls, parameters, or draft changes, enumerate them first and address each one separately; do not analyze them as one blended issue.
- If only one discharge point or one contested limit is truly at issue, state that expressly and explain why.

## 2. Failure modes the skill is correcting
- Drafts rely on generalized environmental concern without tying each objection to the permit condition, fact sheet analysis, and governing standard.
- Drafts miss the comparison between the expiring permit and the draft permit, so anti-backsliding and relaxation of controls are not tested.
- Drafts omit or underuse ambient water quality data, receiving-water conditions, and designated-use analysis.
- Drafts ignore compliance history, monitoring frequency, or parameter selection even when those facts bear on permit adequacy.
- Drafts state conclusions without identifying the controlling legal authority behind each objection.
- Drafts read like a summary of concerns rather than a request for agency action supported by law and record evidence.

## 3. Legal frameworks / domain conventions that apply
- Ground each objection in the Clean Water Act permit program and the applicable NPDES permitting regulations, including permit issuance and public participation requirements.
- Test proposed limits against technology-based effluent limits, effluent guideline floors, and any applicable state water quality standards.
- Where technology-based limits are not enough, evaluate water quality-based effluent limits, including how the limits were derived and whether the fact sheet explains the derivation.
- Evaluate anti-backsliding under the Clean Water Act and implementing regulations when the draft permit relaxes or omits prior limits, monitoring, or conditions.
- Evaluate antidegradation where the record suggests increased loading, reduced treatment stringency, or a waterbody at or above its existing-use support level.
- Evaluate any mixing zone authorization under the applicable state water quality standards and permitting rules, including whether the dilution basis is disclosed and defensible.
- Use ambient monitoring, upstream/downstream context, and cumulative loading information to test whether the draft permit is protective of designated uses and numeric criteria.
- Treat the fact sheet, technical support documents, and existing permit as part of the administrative record that must justify each condition.

## 4. Analytical scaffolds
- Start with a short opening summary that states the overall position, the permit being challenged, and the core reasons the draft is inadequate.
- For each objection, use the same internal sequence:
  1. identify the permit condition, outfall, or parameter;
  2. cite the controlling statute, regulation, or permit principle;
  3. explain the factual deficiency in the draft permit or fact sheet;
  4. tie the deficiency to the supporting data in the record;
  5. state the action requested from the agency.
- Compare the draft permit against the expiring permit condition-by-condition:
  - limits,
  - monitoring frequency,
  - sample type,
  - averaging period,
  - reporting or compliance language,
  - narrative conditions tied to wastewater quality.
- For any relaxed or deleted requirement, test whether the record identifies a valid legal basis, including the anti-backsliding framework and any exception the agency claims.
- For any water-quality-based limit, test whether the derivation is disclosed, whether the receiving-water assumptions are accurate, and whether the final limit is stringent enough to protect the relevant criterion and designated use.
- For any claim that dilution or mixing makes the permit acceptable, test whether the mixing-zone basis is authorized, quantified, and consistent with state standards.
- For any ambient data issue, identify whether the record includes recent, relevant, and site-specific information; if not, request additional analysis or permit revision.
- For any compliance-history issue, use it to justify tighter monitoring, clearer conditions, or denial/revision of reissuance if the record shows recurring or unresolved noncompliance.
- When multiple parameters are involved, analyze each parameter separately rather than bundling them into a single generic criticism.
- End each objection with a concrete requested remedy: revise the limit, add monitoring, withdraw the relaxation, require a new analysis, or reopen the record.

## 5. Vertical / structural / temporal relationships
- Use the existing permit as the baseline for all relaxation analysis; a draft permit must be tested against the prior authorized discharge structure, not against an abstract policy goal.
- Treat the fact sheet as the explanation for the permit terms; a weak or missing fact-sheet rationale is itself a substantive defect.
- Read upstream and downstream conditions together when the receiving water is already stressed or when other dischargers affect the same segment.
- Distinguish present operations from future possibilities; the letter should challenge what the draft permit authorizes now, not speculate beyond the record.
- If the draft permit contemplates future studies, deferred modeling, or later recalculation, flag whether immediate protection is still provided in the interim.

## 6. Output structure conventions
- Draft as a formal public comment letter with a professional salutation, permit identification, and a clear statement that the submission is timely.
- Begin with a concise opening summary of objections and the overall requested outcome.
- Follow with numbered issue-by-issue headings in conventional legal style; each issue should include the legal standard, the factual deficiency, the supporting record, and the requested fix.
- Use short, plain-English subheadings where needed to separate anti-backsliding, water-quality-based limits, ambient data, monitoring, mixing zone, antidegradation, and compliance-history objections.
- If warranted by the record, include a request for a public hearing or further technical briefing.
- Close with a specific conclusion section that restates the relief requested and preserves the commenter’s position for the administrative record.
- Use formal letter conventions throughout, including submitter identification and permit reference, and ensure the named output filename matches the task instruction exactly.