osed

Draft the formal legal instrument itself — a Clean Water Act §505 (or other citizen-suit) Notice of Intent to Sue, an administrative rulemaking petition, a deadline complaint, or a consent-decree settlement scaffold. Use this skill whenever the user wants to produce, fill in, or revise one of these instruments, or says things like "draft the notice," "write the petition," "put together the 60-day letter," "we need a complaint for the missed deadline," or "scaffold a settlement." Works from a completed Gap Analysis when one exists. Produces a clearly-marked DRAFT with judgment-call fields flagged for attorney review — never a filing-ready or signed document.

Read a statute or regulation and identify where an agency has failed to perform a mandatory, deadline-bound duty. Use this skill whenever the user wants to find actionable agency failures, audit a statute for missed deadlines, build the factual basis for a deadline suit or unreasonable-delay suit, or check whether a "shall by [date]" obligation has gone unmet. Trigger this even when the user only says things like "has the agency done what the law requires," "find the gaps in this statute," "what deadlines did EPA miss," or describes a regulatory program they think is behind schedule. Produces a structured findings table, never a decision to sue.

The front door. Use this skill when a non-lawyer describes an environmental problem or situation in everyday terms and does not yet know which law, agency, or instrument applies — "the creek by us smells bad and the county keeps approving permits," "our air is bad near the refinery, what can we do," "who do we even complain to about a pipeline," "is there anything we can do about the landfill." It diagnoses the likely legal pathways and routes the user to the right next step. It never tells the user they have a case, never says a named party broke the law, never predicts outcomes — it identifies candidate pathways and hands off.

The conductor. Use this skill when a user wants the whole OSED process run end-to-end on an environmental concern — "take my situation through the whole process," "run the full pipeline and put together the package," "do all the steps," "I described the problem, now build the package for my attorney." It runs intake → Gap Analysis → Drafting ↔ Precedent Retrieval → Plain-Language, carries each artifact into the next, and assembles a single flagged DRAFT case package with a consolidated attorney checklist. It automates the handoffs only — it never resolves a judgment call, never decides the merits, and always stops at a licensed attorney.

Translate a legal pathway, instrument, or doctrine into plain terms a non-lawyer can actually act on — a community group, a county commission, an organizer, a concerned resident. Use this skill whenever the user wants a legal concept explained for a lay audience, asks "what does this mean for us," "explain standing in plain English," "how would a community group actually use a state environmental rights act," or needs an instrument or process made legible without jargon. Especially apt for state environmental-rights-act pathways and citizen-suit mechanics. Explains and clarifies; never gives legal advice, predicts outcomes, or tells the reader they have a case.

1 hook across 1 event