1. Load

   ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

   → jurisdiction, practice areas, warning-day cadence.
2. Use the workflow below.
3. Route by flag:

   • --add

     : capture case, type, description, due date, source, owner. Write to

     ~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml

     . Check for duplicates first.

   • --report

     (default): cross-case rollup — overdue, next 3d, next 7d, next 14d; by owner; by practice area; unassigned flags.

   • --update [id]

     : modify fields; log note with date.

   • --complete [id]

     : mark done; confirm with student that work is actually filed/submitted.

   • --close [id]

     : close-without-completing; require rationale in notes.
4. Confirm any write before committing.

• ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

  → jurisdiction, practice areas, deadline warning days (default 14/7/3/1), supervising attorneys

• ~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml

  — the ledger

• Case ID + name (which case)
• Practice area
• Type (filing / hearing / statute-of-limitations / discovery / cure-period / response / notice / other)
• Description — one line of what's due
• Due date (and time + timezone if applicable)
• Source — where the deadline came from (court order served 2026-04-20, statute 8 USC § 1229a, cure period in contract §7)
• Owner student — the student responsible

id

[case]-[short-desc]-[YYYY-MM]

/client-intake

/draft

/status

references/plausibility-bands/{state}.md

{state}

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

references/plausibility-bands/CA.md

references/plausibility-bands/IL.md

references/plausibility-bands/{state}.md

"I don't have deadline plausibility checks for [state] — the sanity band for this clinic's jurisdiction isn't in the shipped reference files. I can still track deadlines (add, report, update, complete, close), but I cannot sanity-check them against typical ranges. Here's how to build the band file from your state's rules: copy

references/plausibility-bands/IL.md

as a template, fill in one row per deadline type your clinic sees most (typical range, triggering-event handling, computation-of-time rule, short cite), save at

references/plausibility-bands/{state}.md

, and re-run

/legal-clinic:deadlines

. Until then, every deadline I accept will carry

warnings: no-plausibility-band

and your review should treat dates as unchecked."

1. Load the bands table for this clinic's jurisdiction from

   references/plausibility-bands/{state}.md

   (plus federal-always).
2. After the student enters

   due:

   , compare to triggering-event date + typical range for that

   type:

   (if a typical range exists in the loaded band file for the filing type).
3. If inside the range, write the entry. Say nothing — the band exists to catch errors, not to congratulate correct math.
4. If outside the range by a material margin, stop before writing and say:

   The date you entered falls outside the typical range for [type] in [jurisdiction]. [Type] deadlines for [filing type] typically fall ~[range] after [triggering event]. Your entry: [date], which is [N] days from [triggering event]. Re-check your calculation against [cited rule from the band file] and the jurisdiction's computation-of-time rule. If your calculation is correct (local rule exception, atypical triggering event, tolling, waiver), confirm and I will add the entry as-is. Otherwise, recompute and re-run

   /deadlines --add

   .

5. If no band is known for this

   type:

   (unusual filing, non-standard deadline), do not sanity-check — write the entry and note in the

   warnings:

   field that no plausibility band applies.
6. If the band file is missing entirely for this jurisdiction, the hard stop above applies at cold-start; in steady-state (supervisor acknowledged the gap and proceeded), every entry is written with

   warnings: no-plausibility-band

   .

[VERIFY]

due:

due: [VERIFY]

• Sets

  status: completed

  ,

  completed_date: [today]

  .
• Confirms with the student that the actual work is done and filed/submitted.
• Removes from active reports but stays in the yaml.

• /client-intake

  : when intake surfaces a timeline urgency (eviction notice date, asylum filing deadline, hearing date), offer to

  /deadlines --add

  with pre-populated fields.

• /draft

  : when a filing draft references a deadline (answer due, objection window), offer to add.

• /status

  : the status skill reads

  ~/.claude/plugins/config/claude-for-legal/legal-clinic/deadlines.yaml

  for the relevant case and includes upcoming deadlines in its output.

• /semester-handoff

  : reads deadlines.yaml to identify all active deadlines across departing-student cases; each handoff memo carries the deadlines forward.

• /supervisor-review-queue

  (if formal review enabled): deadlines near their cutoff get priority in the review queue.

• Calculate deadlines from triggering events. If a complaint was served today and the answer is due in 21 days per local rules, the skill doesn't do that math — the student does, using the rule, and logs the resulting date. (Doing the math autonomously creates a liability the skill shouldn't own; rules vary by jurisdiction and court.)
• File or serve anything. The skill tracks dates; filing happens outside the plugin.
• Auto-notify. No scheduled notifications. The report surfaces warnings when invoked; it doesn't push. A scheduled cron could be added later but would need explicit professor opt-in per clinic.
• Override local rules. If the student logs a due date that contradicts local rules, the skill doesn't catch it. Another reason to calendar with

  [VERIFY: confirm against local rule]

  for any non-routine deadline.