Skip to content
Back to skills

Practice Overdue Triage

ASecurity

Investigate explicitly scoped overdue and stale register items, propose sourced dispositions, and route exact approved changes through owning workflows.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 10, 2026
development

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 10, 2026

npx -y skills add lawyered0/lawyeredos --skill practice-overdue-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Practice Overdue Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Practice Overdue Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lawyered0-practice-overdue-triage/badge)](https://www.skillsdirectory.com/skills/lawyered0-practice-overdue-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: practice-overdue-triage
description: Investigate explicitly scoped overdue and stale register items, propose sourced dispositions, and route exact approved changes through owning workflows.
---

# Overdue and stale-item review

This optional instruction module is read through the workflow catalog. It adds
no installed host skill, automatic cleanup or scheduling. Use when the lawyer
requests an overdue/stale sweep; use daily triage for an attention overview.

Sibling skill links identify the shared workflow prose. Actual operations use
the active host's installed owning skill and installed references after the
catalog's dependency check; an absent dependency remains unavailable.

Read [scope and authority](../../workflows/scope-and-authority.md),
[source verification](../../workflows/source-verification.md),
[dates](../../workflows/dates.md) and
[dispositions](references/dispositions.md). Load
[records and handoffs](../../workflows/records-and-handoffs.md) for proposed
writeback. An old date is an alarm, not proof of completion or abandonment.

## Detect and investigate

1. State the agreed register scope, date/timezone, review horizon and source
   limits. Read current rows and available revision/history through
   [matter tracker](../../../skills/practice-matter-tracker/SKILL.md).
2. Flag separately: a supported dated next action past due; possible expired or
   imminent limitation; passed fixed court/order date; missing or malformed
   protective data; missing ownership/next action; and unexplained staleness.
   Do not mine arbitrary prose numbers as dates. Staleness depends on expected
   matter cadence and is a review signal, not a breach.
3. Rank limitations, court compliance and irreversible consequences before
   administrative age. Show unresolved protective concerns immediately.
4. Resolve each candidate matter and read targeted memory, controlling documents
   and relevant correspondence. Capture evidence both for and against
   completion, supersession or a continuing obligation. Record source locators,
   date status, canonical old values and uncertainty. Do not expand into an
   unrelated mailbox or file collection.
5. Mail beyond exact supported matter intake requires an explicitly bounded
   source selection and actually authorized active read/search connector, or
   supplied source-complete messages. Missing/partial evidence means unknown;
   it does not justify removing an item. Never improvise broad acquisition.
6. Assign a reference disposition. Keep unchanged unresolved items in the report.
   A completed filing/service act requires appropriate acceptance/compliance
   evidence; a sent message alone proves neither. The bundled jurisdiction
   profile supplies no deadline calculator. Use a supplied verified calculation
   or a separately authorized suitable calculation facility, with verified legal
   inputs and current sources. Do not substitute generic legal-date arithmetic
   or calculate from the register description alone.

## Propose and apply only approved changes

Lead with unresolved protective items, then show the atomic change table from
the reference. No unattended run clears, removes, closes or reschedules a
limitation or court deadline. Exact lawyer approval is required; generic
"cleanup" does not approve deletion of protective records.

Re-read every approved target before preview/commit; skip changed items and
report drift. Use existing guarded tracker/memory workflows. Inspect uncertain
commit outcomes through their recovery procedures before considering retry.
Verify canonical rows afterward. Calendar is a separate downstream proposal
from final approved tracker state, through
[calendar reconciliation](../../../skills/practice-calendar-sync/SKILL.md); missing calendar
access does not conceal or reverse a register result.

## Completion

Report completed, drift-skipped, failed, outcome-uncertain and still-unresolved
items. A complete sweep gives every detected candidate a documented disposition
and verifies every approved change. Success is not measured by old dates
disappearing. No mailbox mutation, external communication or automatic closure
is authorized here.

Files in this skill

  • SKILL.md4.1 KB
  • references/dispositions.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.