ThomasMoreAI/legal-skills-open / au/litigation/skills/compute-procedural-deadlines-l0cka
compute-procedural-deadlines-l0cka
VerifiedCompute candidate procedural deadlines for Australian civil litigation from a lawyer-supplied trigger event using the bundled deterministic script and evidence-gated computation-rule tables — the model never performs date arithmetic. Computed coverage spans the federal courts and the superior and lower courts of every State and Territory, each with a verified holiday table; steps without a verified table entry receive identify-only output naming the governing rule. Use when a practitioner needs candidate dates for defences, appeals or other rule-fixed steps after filing, service or judgment. Do not use for criminal procedure, for court-fixed or discretionary dates, or when the trigger date is contested — those fail closed to the responsible lawyer, and every computed date is provisional until confirmed.
Compute Procedural Deadlines
Compute candidate deadlines with the bundled script and nothing else. A refusal from the script is a correct result: report the governing rule and the reason, and never fill the gap with model arithmetic.
Read the source and control method, use an approved profile per the deadline profile schema, and run compute_deadline.py against the computation-rule tables and holiday tables.
Workflow
- Fix the trigger and the forum.
- Record the forum, the procedural step, the lawyer-supplied trigger
date and what the trigger was (service, filing, judgment). A contested
or unknown trigger date is
NOT READY— never assume one.
- Record the forum, the procedural step, the lawyer-supplied trigger
date and what the trigger was (service, filing, judgment). A contested
or unknown trigger date is
- Locate the governing rule.
- Find the matching period rule in the forum's computation-rule table.
A step with no table entry is identify-only: name the governing rule
if known and route verification to
$verify-deadline-basis.
- Find the matching period rule in the forum's computation-rule table.
A step with no table entry is identify-only: name the governing rule
if known and route verification to
- Run the script.
- Call
scripts/compute_deadline.pywith the table id, period rule id and trigger date. Report the script's output faithfully:computedresults as candidate dates with the provisions applied and every warning;identify_onlyresults with the stated reason. - Never adjust, round or re-derive a date the script produced or refused. If holiday caveats flag registry-location uncertainty, surface them.
- Call
- Set the human decision gate.
- Name the confirmer who must confirm each candidate date and enter it in the diary system of record before any reliance.
Result contract
Lead with READY FOR HUMAN REVIEW, READY WITH QUALIFICATIONS, NOT READY
or OUTSIDE SCOPE.
Step: <forum; procedural step; governing rule citation>
Trigger: <lawyer-supplied trigger event and date; stated as assumption>
Script result: <computed candidate date and day | identify-only with reason>
Provisions applied: <citations from the script output; evidence states>
Warnings: <script warnings, holiday caveats, staging limits>
Human decision gate: <confirmer; diary entry pending confirmation>
Limitations: <candidate only; not a diary system; script-only arithmetic>
Fail closed
Return NOT READY when the trigger date, forum or governing rule cannot be
established. Report every script refusal as identify-only output — never
compute around an unverified table, an uncovered holiday range or an
unsupported period. Route criminal procedure OUTSIDE SCOPE, and never
present a candidate date as the binding deadline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |