@wonsukchoi/crondex 0.21.0 → 0.23.0

package/jobs/hr/retirement-plan-enrollment-deadline-check.yaml

@@ -0,0 +1,40 @@
+id: retirement-plan-enrollment-deadline-check
+version: 1
+name: Retirement Plan Enrollment Deadline Check
+description: >
+  Flags employees who are eligible for the 401(k)/retirement plan but
+  haven't enrolled or waived as their enrollment deadline approaches. Use
+  this if someone has ever missed the window to make an active election
+  and got dropped into a default auto-enrollment deferral rate they didn't
+  actually want.
+category: hr
+tags: [hr, retirement, 401k, benefits, deadline]
+schedule: "0 8 * * 1"
+timezone: "America/New_York"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "ENROLLMENT DEADLINE: %s — eligible since %s, deadline %s (%d days), no election on file\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{retirement_tracking_csv_path}}"
+variables:
+  retirement_tracking_csv_path:
+    default: "./retirement-plan-tracking.csv"
+    description: "Path to a CSV with columns: employee_name,eligibility_date (YYYY-MM-DD),enrollment_deadline (YYYY-MM-DD),election_status (enrolled/waived, blank if no election yet)."
+  warn_days_before:
+    default: 14
+    description: How many days before the enrollment deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Many plans auto-enroll non-responders at a default deferral rate after
+  the deadline rather than defaulting to no contribution — confirm your
+  plan document's actual default behavior rather than assuming.

package/jobs/hr/workers-comp-claim-status-check.yaml

@@ -0,0 +1,42 @@
+id: workers-comp-claim-status-check
+version: 1
+name: Workers' Comp Claim Status Check
+description: >
+  Checks open workers' compensation claims with the carrier and flags ones
+  that have gone quiet or are approaching an expected return-to-work date
+  with no update. Use this if an injured employee's claim has ever
+  stalled with the carrier for weeks with nobody at the company noticing
+  or following up.
+category: hr
+tags: [hr, workers-comp, compliance, safety]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{wc_carrier}} for open workers' compensation claims and
+  cross-reference against {{hris_system}} for each claimant's expected
+  return-to-work date, if any.
+  1. List each open claim: employee name, date of injury, days since last
+     status update, and expected return date (if set).
+  2. Flag any claim with no status update in the last {{stale_days}} days,
+     or with a return date within {{escalate_within_days}} days and no
+     recent update, as needing a follow-up call with the carrier.
+  3. If everything is progressing normally, say so in one line.
+variables:
+  wc_carrier:
+    default: "your workers' compensation carrier/TPA"
+    description: Where claim status is tracked (the insurance carrier or third-party administrator portal).
+  hris_system:
+    default: "your HRIS"
+    description: Where employee return-to-work dates and leave status are recorded.
+  stale_days:
+    default: 14
+    description: Days with no status update before a claim is flagged as stalled.
+  escalate_within_days:
+    default: 7
+    description: Days before an expected return date at which a claim with no recent update becomes urgent.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Read-only status check — actually contacting the carrier, adjusting
+  duties, or making return-to-work decisions is for HR/legal/safety to
+  handle. No generic script mode since carrier portals vary widely.

package/jobs/insurance/adjuster-caseload-balance-check.yaml

@@ -0,0 +1,45 @@
+id: adjuster-caseload-balance-check
+version: 1
+name: Adjuster Caseload Balance Check
+description: >
+  Counts open claims assigned per adjuster and flags anyone carrying a
+  caseload well above the team average, so work can be redistributed
+  before it hurts claim cycle time. Use this if one adjuster has ever
+  quietly ended up with double the caseload of everyone else on the team.
+category: insurance
+tags: [insurance, claims, adjuster, caseload, operations]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v overload="{{overload_multiplier}}" '
+    NR==1 {next}
+    {
+      count[$2]++;
+      total++;
+      n_adjusters[$2]=1;
+    }
+    END {
+      n=0;
+      for (a in n_adjusters) n++;
+      avg = (n > 0) ? total / n : 0;
+      printf "CASELOAD SUMMARY: %d open claims across %d adjusters (avg %.1f)\n", total, n, avg;
+      for (a in count) {
+        if (avg > 0 && count[a] > avg * overload) {
+          printf "OVERLOADED: %s — %d open claims (avg %.1f)\n", a, count[a], avg;
+        }
+      }
+    }
+  ' "{{open_claims_by_adjuster_csv}}"
+variables:
+  open_claims_by_adjuster_csv:
+    default: "./open-claims-by-adjuster.csv"
+    description: "Path to a CSV with columns: claim_number,adjuster_name — one row per open claim."
+  overload_multiplier:
+    default: 1.5
+    description: How many times the team average caseload counts as overloaded (e.g. 1.5 = 50% above average).
+compatible_agents: [generic, claude, codex]
+notes: >
+  Staffing-balance check across a claims team, distinct from
+  claims-aging-backlog-tracker which looks at claim age rather than
+  who's handling how many claims.

package/jobs/insurance/agent-broker-license-expiry-tracker.yaml

@@ -0,0 +1,40 @@
+id: agent-broker-license-expiry-tracker
+version: 1
+name: Agent/Broker License Expiry Tracker
+description: >
+  Checks producer (agent/broker) license and appointment expiration dates
+  across every state they're licensed in and flags anything expiring
+  soon. Use this if an agent has ever kept writing business in a state
+  after their license quietly lapsed.
+category: insurance
+tags: [insurance, agent, broker, license, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline expiry_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (expiry_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        status = (diff_days < 0) ? "EXPIRED" : "EXPIRING";
+        printf "%s: %s — %s license/appointment in %s expires %s (%d days)\n", status, $1, $2, $2, $3, diff_days;
+      }
+    }
+  ' "{{producer_licenses_csv_path}}"
+variables:
+  producer_licenses_csv_path:
+    default: "./producer-licenses.csv"
+    description: "Path to a CSV with columns: producer_name,state,expiry_date (YYYY-MM-DD) — one row per state license/appointment."
+  warn_days_before:
+    default: 45
+    description: How many days before a license or appointment expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks producer (selling agent/broker) licensing compliance across an
+  agency or MGA's distribution force — distinct from
+  certificate-of-insurance-request-check, which tracks COI requests, not
+  producer licensure.

package/jobs/insurance/cat-event-exposure-monitor.yaml

@@ -0,0 +1,37 @@
+id: cat-event-exposure-monitor
+version: 1
+name: Catastrophe Event Exposure Monitor
+description: >
+  Cross-references active policies against a catastrophe (hurricane,
+  wildfire, earthquake, flood) event footprint and estimates
+  policy-count and total insured value exposure inside the impact zone.
+  Use this if a CAT event has ever hit before anyone had a fast answer to
+  "how many policies do we have in that area, and what's our exposure."
+category: insurance
+tags: [insurance, catastrophe, cat, exposure, risk]
+schedule: "0 */6 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Given the active/forecast catastrophe event: {{cat_event_description}},
+  and the policy exposure summary: {{policy_exposure_summary}}.
+  1. Estimate how many policies and how much total insured value fall
+     within or near the event's impact footprint.
+  2. Break this down by line of business (property, auto, etc.) if the
+     exposure data allows it.
+  3. Flag any single large-limit policy that falls inside the footprint
+     for individual review.
+  4. Note this is a rough triage estimate for readiness/response
+     planning, not a final claims or reserve figure.
+variables:
+  cat_event_description:
+    default: "describe the catastrophe event and its current/forecast footprint here"
+    description: Name, type, and geographic footprint of the catastrophe event being tracked.
+  policy_exposure_summary:
+    default: "paste or summarize policy counts and insured values by geography here"
+    description: Summary of active policy counts and total insured value by geography/line of business.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Pre/during-event exposure estimation for claims and reinsurance
+  readiness planning — distinct from claims-aging-backlog-tracker, which
+  tracks already-filed claims rather than pre-loss exposure.

package/jobs/insurance/claims-aging-backlog-tracker.yaml

@@ -0,0 +1,48 @@
+id: claims-aging-backlog-tracker
+version: 1
+name: Claims Aging & Backlog Tracker
+description: >
+  Buckets open claims by how long they've been open (0-30, 31-60, 61-90,
+  90+ days) and flags any bucket that's grown past target so a claims
+  manager can rebalance the queue. Use this if a backlog of aging claims
+  has ever crept up gradually until a regulator or auditor asked why so
+  many were still open past 90 days.
+category: insurance
+tags: [insurance, claims, aging, backlog, operations]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v cap90="{{max_90plus_pct}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline opened_epoch; close(cmd);
+      age_days = (today - opened_epoch) / 86400;
+      total++;
+      if (age_days <= 30) b30++;
+      else if (age_days <= 60) b60++;
+      else if (age_days <= 90) b90++;
+      else b90plus++;
+    }
+    END {
+      printf "AGING SUMMARY: 0-30d=%d 31-60d=%d 61-90d=%d 90d+=%d (total=%d)\n", b30, b60, b90, b90plus, total;
+      pct90plus = (total > 0) ? (b90plus / total) * 100 : 0;
+      if (pct90plus > cap90) {
+        printf "OVER TARGET: %.1f%% of open claims are 90+ days old (cap %d%%)\n", pct90plus, cap90;
+      }
+    }
+  ' "{{open_claims_csv_path}}"
+variables:
+  open_claims_csv_path:
+    default: "./open-claims.csv"
+    description: "Path to a CSV with columns: claim_number,date_opened (YYYY-MM-DD)."
+  max_90plus_pct:
+    default: 10
+    description: Maximum acceptable percentage of open claims sitting at 90+ days before this counts as over target.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Portfolio-level aging distribution for a claims team, distinct from
+  claim-status-check which follows up on individual stale claims for a
+  single policyholder.

package/jobs/insurance/doi-filing-deadline-tracker.yaml

@@ -0,0 +1,42 @@
+id: doi-filing-deadline-tracker
+version: 1
+name: State DOI Regulatory Filing Deadline Tracker
+description: >
+  Warns before a state Department of Insurance filing deadline (rate
+  filings, annual statements, market conduct reports) so nothing gets
+  submitted late. Use this if a regulatory filing has ever gone out late
+  because the deadline lived only in one compliance person's memory.
+category: insurance
+tags: [insurance, compliance, regulatory, doi, filing]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        status = (diff_days < 0) ? "OVERDUE" : "DUE SOON";
+        printf "%s: %s — %s filing due %s (%d days)\n", status, $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{doi_filings_csv_path}}"
+variables:
+  doi_filings_csv_path:
+    default: "./doi-filings.csv"
+    description: "Path to a CSV with columns: state,filing_type,due_date (YYYY-MM-DD),filed_date (blank if not yet filed)."
+  warn_days_before:
+    default: 21
+    description: How many days before a filing deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Regulatory filing deadlines owed to state insurance regulators —
+  distinct from legal's compliance-filing-deadline-reminder, which is a
+  generic cross-industry filing tracker; this one is scoped specifically
+  to insurance-department filings (rate filings, annual statements,
+  market conduct reports).

package/jobs/insurance/loss-ratio-by-line-monitor.yaml

@@ -0,0 +1,43 @@
+id: loss-ratio-by-line-monitor
+version: 1
+name: Loss Ratio by Line of Business Monitor
+description: >
+  Calculates the incurred loss ratio for each line of business and flags
+  any line running hotter than target, so underwriting or pricing can
+  react before a bad quarter turns into a bad year. Use this if a line's
+  loss ratio has ever drifted well past target for months before anyone
+  noticed in the numbers.
+category: insurance
+tags: [insurance, loss-ratio, underwriting, finance]
+schedule: "0 7 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{target_loss_ratio_pct}}" '
+    NR==1 {next}
+    {
+      earned[$1] += $2;
+      incurred[$1] += $3;
+    }
+    END {
+      for (line in earned) {
+        if (earned[line] > 0) {
+          ratio = (incurred[line] / earned[line]) * 100;
+          flag = (ratio > target) ? " OVER TARGET" : "";
+          printf "%s: loss ratio %.1f%%%s (earned %.2f, incurred %.2f)\n", line, ratio, flag, earned[line], incurred[line];
+        }
+      }
+    }
+  ' "{{loss_ratio_csv_path}}"
+variables:
+  loss_ratio_csv_path:
+    default: "./loss-ratio-by-line.csv"
+    description: "Path to a CSV with columns: line_of_business,earned_premium,incurred_losses — one row per period/line entry, aggregated across the current reporting period."
+  target_loss_ratio_pct:
+    default: 65
+    description: Target maximum loss ratio percentage per line of business before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Financial performance monitoring by line of business for underwriting
+  and actuarial review — distinct from claims-aging-backlog-tracker,
+  which tracks claim handling speed rather than loss cost.

package/jobs/insurance/policy-lapse-rate-monitor.yaml

@@ -0,0 +1,41 @@
+id: policy-lapse-rate-monitor
+version: 1
+name: Policy Cancellation & Lapse Rate Monitor
+description: >
+  Calculates the weekly policy cancellation/lapse rate and flags it when
+  it climbs past a healthy baseline, so retention teams can react before
+  a leaky book turns into a shrinking one. Use this if a rising lapse
+  rate has ever gone unnoticed until a quarterly report showed the book
+  had quietly shrunk.
+category: insurance
+tags: [insurance, retention, lapse, cancellation, operations]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v baseline="{{baseline_lapse_pct}}" '
+    NR==1 {next}
+    {
+      total++;
+      if ($2 == "cancelled" || $2 == "lapsed") lapsed++;
+    }
+    END {
+      pct = (total > 0) ? (lapsed / total) * 100 : 0;
+      printf "LAPSE RATE: %.1f%% (%d of %d policies) — baseline %d%%\n", pct, lapsed, total, baseline;
+      if (pct > baseline) {
+        printf "ABOVE BASELINE: lapse rate exceeds the %d%% target\n", baseline;
+      }
+    }
+  ' "{{policy_status_csv_path}}"
+variables:
+  policy_status_csv_path:
+    default: "./policy-status-weekly.csv"
+    description: "Path to a CSV with columns: policy_number,status (active/cancelled/lapsed) for the current reporting period's book."
+  baseline_lapse_pct:
+    default: 8
+    description: Baseline acceptable cancellation/lapse rate percentage before it's flagged as elevated.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Book-wide retention health metric, distinct from
+  premium-payment-delinquency-tracker, which flags individual accounts
+  rather than the aggregate lapse trend.

package/jobs/insurance/premium-payment-delinquency-tracker.yaml

@@ -0,0 +1,42 @@
+id: premium-payment-delinquency-tracker
+version: 1
+name: Premium Payment Delinquency Tracker
+description: >
+  Scans the book of business for policyholders past due on premium
+  payments and flags accounts approaching cancellation-for-nonpayment, so
+  collections or retention outreach can happen before a policy lapses.
+  Use this if delinquent accounts have ever piled up unnoticed until a
+  batch of policies cancelled all at once.
+category: insurance
+tags: [insurance, premium, delinquency, collections, retention]
+schedule: "0 7 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v cancel_days="{{cancellation_grace_days}}" '
+    NR==1 {next}
+    $3 != "unpaid" {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      past_due_days = (today - due_epoch) / 86400;
+      if (past_due_days > 0) {
+        remaining = cancel_days - past_due_days;
+        status = (remaining <= 0) ? "CANCELLATION ELIGIBLE" : sprintf("%d days until cancellation-eligible", remaining);
+        printf "DELINQUENT: %s — due %s, %d days past due — %s\n", $1, $2, past_due_days, status;
+      }
+    }
+  ' "{{book_of_business_csv_path}}"
+variables:
+  book_of_business_csv_path:
+    default: "./premium-payment-status.csv"
+    description: "Path to a CSV with columns: policy_number,payment_due_date (YYYY-MM-DD),status (paid/unpaid)."
+  cancellation_grace_days:
+    default: 30
+    description: Days past due before a policy becomes eligible for cancellation-for-nonpayment.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Book-wide delinquency and collections view across many policyholders,
+  distinct from premium-payment-due-reminder, which reminds a single
+  policyholder about their own upcoming payment before it's even late.

package/jobs/insurance/quote-to-bind-conversion-tracker.yaml

@@ -0,0 +1,41 @@
+id: quote-to-bind-conversion-tracker
+version: 1
+name: Quote-to-Bind Conversion Rate Tracker
+description: >
+  Calculates the quote-to-bind conversion rate over the trailing period
+  and flags it when it drops below target, so sales/underwriting leaders
+  catch a pricing or process problem while it's still small. Use this if
+  a falling close rate has ever gone unnoticed for a full quarter because
+  nobody was watching quotes lost, only policies written.
+category: insurance
+tags: [insurance, sales, quoting, conversion, underwriting]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{target_conversion_pct}}" '
+    NR==1 {next}
+    {
+      quotes++;
+      if ($2 == "bound") bound++;
+    }
+    END {
+      pct = (quotes > 0) ? (bound / quotes) * 100 : 0;
+      printf "CONVERSION RATE: %.1f%% (%d of %d quotes bound) — target %d%%\n", pct, bound, quotes, target;
+      if (pct < target) {
+        printf "BELOW TARGET: conversion rate is under the %d%% target\n", target;
+      }
+    }
+  ' "{{quotes_csv_path}}"
+variables:
+  quotes_csv_path:
+    default: "./quotes-weekly.csv"
+    description: "Path to a CSV with columns: quote_id,status (bound/lost/pending) for the trailing reporting period."
+  target_conversion_pct:
+    default: 25
+    description: Target minimum quote-to-bind conversion rate percentage before this is flagged as below target.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Sales-funnel metric for new business production, distinct from
+  underwriting-queue-sla-monitor, which measures decision speed rather
+  than the rate at which quotes actually convert to bound policies.

package/jobs/insurance/reinsurance-treaty-renewal-tracker.yaml

@@ -0,0 +1,38 @@
+id: reinsurance-treaty-renewal-tracker
+version: 1
+name: Reinsurance Treaty Renewal Tracker
+description: >
+  Warns before a reinsurance treaty's renewal or non-renewal notice date
+  so terms can be renegotiated or the market re-shopped in time. Use this
+  if a treaty has ever auto-renewed on unfavorable terms because the
+  notice window quietly passed.
+category: insurance
+tags: [insurance, reinsurance, treaty, renewal]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline notice_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (notice_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "NOTICE DEADLINE APPROACHING: %s (%s) — non-renewal notice due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{treaties_csv_path}}"
+variables:
+  treaties_csv_path:
+    default: "./reinsurance-treaties.csv"
+    description: "Path to a CSV with columns: treaty_name,reinsurer,non_renewal_notice_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 60
+    description: How many days before the non-renewal notice deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks the reinsurer-facing treaty notice deadline, not a primary
+  policy renewal — distinct in scope from policy-renewal-reminder, which
+  tracks retail/commercial policies sold to policyholders.

package/jobs/insurance/siu-fraud-referral-tracker.yaml

@@ -0,0 +1,36 @@
+id: siu-fraud-referral-tracker
+version: 1
+name: SIU Fraud Referral Tracker
+description: >
+  Checks claims referred to the Special Investigations Unit for suspected
+  fraud and flags any referral that hasn't been triaged or closed within
+  the target window. Use this if a fraud-flagged claim has ever sat in an
+  SIU queue for months with no documented outcome.
+category: insurance
+tags: [insurance, siu, fraud, claims, compliance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the SIU referral log: {{siu_referrals_summary}}.
+  1. List each open referral: claim number, referral date, referral
+     reason, and current SIU status.
+  2. Flag any referral open longer than {{triage_sla_days}} days without
+     a documented triage decision (accept for investigation, decline,
+     refer to law enforcement, or close as unsubstantiated).
+  3. For referrals nearing a statutory reporting deadline, note that
+     explicitly so it doesn't get missed.
+  4. Do not draw conclusions about guilt — flag for human SIU review only.
+variables:
+  siu_referrals_summary:
+    default: "paste or summarize the current SIU referral log here"
+    description: Summary or export of claims currently referred to the Special Investigations Unit.
+  triage_sla_days:
+    default: 15
+    description: Days a referral can sit without a documented triage decision before it's flagged.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Fraud-investigation triage tracking, distinct from
+  claims-aging-backlog-tracker which tracks ordinary claim age rather
+  than SIU investigation status. Sensitive — restrict access to the SIU
+  team and legal/compliance.

package/jobs/insurance/subrogation-recovery-tracker.yaml

@@ -0,0 +1,41 @@
+id: subrogation-recovery-tracker
+version: 1
+name: Subrogation Recovery Tracker
+description: >
+  Checks open subrogation files against at-fault third parties and flags
+  ones with no recovery activity in a while, so pursuit doesn't quietly
+  stall until the statute of limitations closes the door. Use this if a
+  recoverable claim has ever gone unpursued long enough to lose the
+  chance at reimbursement entirely.
+category: insurance
+tags: [insurance, subrogation, recovery, claims]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the open subrogation file list: {{subrogation_files_summary}}.
+  1. List each open file: claim number, at-fault party, recovery amount
+     sought, and date of last recovery activity.
+  2. Flag any file with no activity in more than {{stale_after_days}}
+     days as needing follow-up (demand letter, arbitration filing, or
+     status call to the at-fault carrier).
+  3. Separately flag any file approaching its statute-of-limitations
+     deadline within {{sol_warn_days}} days as urgent.
+  4. Draft a short follow-up note for each stale file, referencing the
+     claim number and recovery amount.
+variables:
+  subrogation_files_summary:
+    default: "paste or summarize the current open subrogation file list here"
+    description: Summary or export of open subrogation recovery files.
+  stale_after_days:
+    default: 21
+    description: Days without recovery activity before a file is flagged as stale.
+  sol_warn_days:
+    default: 45
+    description: Days before a statute-of-limitations deadline to flag a file as urgent.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Tracks pursuing reimbursement from an at-fault third party after a
+  claim is paid — a different direction and timeline from
+  claim-status-check, which tracks the insurer's own claim to the
+  policyholder before payment.

package/jobs/insurance/underwriting-queue-sla-monitor.yaml

@@ -0,0 +1,45 @@
+id: underwriting-queue-sla-monitor
+version: 1
+name: Underwriting Queue SLA Monitor
+description: >
+  Checks pending underwriting submissions against the target
+  turnaround-time SLA and flags any that are approaching or past it. Use
+  this if a broker submission has ever sat in an underwriter's queue for
+  weeks with no decision because nobody was watching the clock.
+category: insurance
+tags: [insurance, underwriting, sla, queue]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v sla="{{sla_days}}" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline submitted_epoch; close(cmd);
+      age_days = (today - submitted_epoch) / 86400;
+      remaining = sla - age_days;
+      if (remaining <= 0) {
+        printf "SLA BREACHED: %s (%s) submitted %s — %d days in queue, SLA is %d\n", $1, $3, $2, age_days, sla;
+      } else if (remaining <= warn) {
+        printf "SLA AT RISK: %s (%s) submitted %s — %d days remaining\n", $1, $3, $2, remaining;
+      }
+    }
+  ' "{{submissions_csv_path}}"
+variables:
+  submissions_csv_path:
+    default: "./underwriting-submissions.csv"
+    description: "Path to a CSV with columns: submission_id,submitted_date (YYYY-MM-DD),underwriter,decision_date (blank if undecided)."
+  sla_days:
+    default: 10
+    description: Target number of business days to reach a decision from submission.
+  warn_days_before:
+    default: 2
+    description: Days before the SLA deadline to start flagging a submission as at-risk.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks new-business/renewal underwriting decision turnaround, distinct
+  from endorsement-request-followup-check which tracks mid-term policy
+  change requests after a policy is already bound.