# Identify Issues In Environmental Impact Statement > Guides preparation of a memorandum for review of an environmental impact statement for a utility-scale energy project by identifying analytical deficiencies, consultation adequacy issues, cultural resources obligations, and socioeconomic analysis gaps that may create legal vulnerability to challenge. - Skill: `finchipaiorg/identify-issues-in-environmental-impact-statement` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/identify-issues-in-environmental-impact-statement` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/identify-issues-in-environmental-impact-statement/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/identify-issues-in-environmental-impact-statement --- # Skill: Identify Issues in Environmental Impact Statement for Utility-Scale Solar Project ## 1. Subject-matter triage - Determine whether the record is primarily federal NEPA review, state environmental review, or a hybrid record, and adjust the legal lens accordingly. - Identify the project footprint, interconnection or storage components, construction phasing, and any offsite or transmission-related elements that may expand the review area. - Separate the FEIS body from supporting studies, appendices, agency correspondence, consultation records, maps, and mitigation commitments; treat the full administrative record as the unit of analysis. - If the record contains multiple resource types, issues, phases, or geographic subareas, enumerate them before analysis and assess each on its own record support. ## 2. Failure modes the skill is correcting - Reviews the main environmental impact statement narrative without cross-referencing technical appendices, agency comments, and consultation materials that may reveal deficiencies not visible in the core text. - Identifies impact categories analyzed without testing the adequacy of the methodology, assumptions, baseline data, or temporal scope used for each analysis. - Treats cultural resources, tribal consultation, and historic preservation obligations as secondary rather than independent legal issues. - Omits agency comment letters and other record objections as sources of concrete vulnerabilities already identified by reviewers. - Collapses distinct issues into one generalized criticism instead of tying each issue to a specific section, authority, record source, and consequence. - States deficiencies without identifying severity, legal consequence, and a concrete next-step challenge or mitigation path. - Concludes from a legal proposition without naming the controlling NEPA, ESA, NHPA, or related authority supporting it. ## 3. Legal frameworks / domain conventions that apply - NEPA: hard-look review, purpose-and-need framing, reasonable range of alternatives, cumulative effects, mitigation discussion, and response-to-comments obligations under 42 U.S.C. §§ 4321 et seq. and 40 C.F.R. Parts 1500–1508. - Administrative law review: arbitrary-and-capricious challenges, inadequate explanation, failure to consider important aspects, and record-based review under the APA, 5 U.S.C. § 706. - Endangered Species Act: consultation duties, biological opinions, incidental take terms, and reasonable and prudent alternatives under 16 U.S.C. § 1536 and implementing regulations. - Migratory bird and wildlife protection rules: assess whether avian and other wildlife impacts were evaluated with a legally meaningful mitigation and monitoring framework. - Historic preservation and tribal consultation: Section 106 review under 54 U.S.C. § 306108 and 36 C.F.R. Part 800, including identification of historic properties, effects analysis, and government-to-government consultation where applicable. - Environmental justice and socioeconomic review: assess whether minority, low-income, tribal, and other affected communities were evaluated using a coherent methodology and adequate baseline. - Air, noise, water, glint/glare, traffic, visual, agricultural, and land-use impacts: these often require appendix-level review and cross-checking against mitigation commitments and assumptions. - Cumulative impacts and connected actions: evaluate whether the FEIS properly captures related projects, shared facilities, and foreseeable buildout effects. - State or local environmental review, siting, or permitting regimes: identify parallel procedural or substantive obligations if present in the record. ## 4. Analytical scaffolds - Start with a record map: FEIS core text, appendices, technical studies, consultation correspondence, agency comments, and mitigation commitments. - For each issue category, identify the exact document section or appendix, the governing authority, the deficiency, the evidence in the record, and the practical consequence. - Use an explicit ordinal severity scale defined once at the top of the memo, and apply it consistently to every issue. - For each issue, tie the deficiency to at least one cross-document dependency: a comment letter, permit condition, consultation document, mitigation table, or technical appendix that changes the analysis. - Evaluate not only whether an impact was mentioned, but whether the methodology, assumptions, geographic scope, temporal horizon, and baseline data support the conclusion. - Test whether mitigation is merely aspirational or is specific, enforceable, and supported by monitoring, triggers, and responsible parties. - For alternatives, assess whether the FEIS considered a reasonable spectrum, explained exclusions, and connected the chosen alternative to the stated purpose and need. - For consultation-driven issues, assess timing, completeness, agency coordination, and whether the consultation record supports the final decision. - For socioeconomic issues, test the data source, population baseline, employment and tax assumptions, displacement or nuisance effects, and environmental justice treatment. - When analyzing comments, distinguish between objections answered with substantive record support and objections answered with conclusory assurances. - For each issue, close the analysis with: scale or magnitude drawn from the record; interaction with another document or permit term; and the downstream legal, regulatory, operational, or litigation consequence. ## 5. Vertical / structural / temporal relationships - Consultation timing matters: late, incomplete, or post-decision consultation can independently undermine the FEIS and may require supplementation. - Earlier studies may be superseded by later maps, surveys, revised layouts, or mitigation commitments; use the latest record version controlling the final analysis. - Conditions embedded in permits, memoranda, or mitigation plans may cure or worsen a FEIS deficiency depending on specificity and enforceability. - Site layout changes, phased buildout, or associated transmission/storage components can expand the impact area and reopen analysis obligations. - If a regional conservation or planning framework applies, test whether the FEIS is consistent with the plan’s conservation design, siting constraints, or avoidance priorities. - Where a later agency action depends on FEIS assumptions, identify whether the FEIS supports that downstream action or leaves a vulnerability that will carry forward. ## 6. Output structure conventions - Write the deliverable as an issues memorandum, not a narrative summary. - Open with a short Executive Summary that states overall vulnerability and the main issue clusters. - Define the severity scale once near the start, then use it uniformly in the issue list. - Use a conventional issue-by-issue format for each entry: - Issue title - Severity - Record location - Governing authority - Deficiency - Supporting record evidence - Cross-reference to related appendix/comment/consultation material - Consequence or litigation risk - Recommended challenge or remediation path - Include a summary table that allows the reader to scan issue, severity, authority, and consequence. - Include a legal vulnerability assessment that synthesizes whether the record is most exposed on alternatives, consultation, cumulative impacts, mitigation, or socioeconomic analysis. - End with a Recommended Next Steps block that gives imperative actions, identifies the responsible role where discernible, and ties each action to an immediate milestone or review deadline. - Use industry-conventional headings rather than any hidden rubric-driven section list. - The filename must be exactly `feis-issue-memorandum.docx`.