litigation-deadline-calendar
Calendar litigation and arbitration deadlines from a scheduling order. Parses a PDF scheduling order, identifies key dates, computes backward deadlines using the applicable rules (Colorado CRCP, Federal FRCP, or arbitration forum rules for AAA/JAMS), and generates an .ics calendar file for Outlook or Google Calendar import. Use this skill whenever the user mentions: litigation deadlines, scheduling order, case management order, deadline calendaring, discovery deadlines, trial preparation deadlines, arbitration scheduling, or anything related to computing or tracking court or arbitration deadli
npx skills add lawve-ai/awesome-legal-skills --skill litigation-deadline-calendar-dave-marcus --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Litigation Deadline Calendar This skill takes a scheduling order (PDF upload), determines the applicable procedural rules, extracts key dates, computes all backward deadlines, and generates an .ics calendar file the user can import into Outlook or Google Calendar. ## Quick Start Workflow 1. **Gather information** from the user 2. **Parse the scheduling order** PDF 3. **Verify the rules** are current 4. **Compute deadlines** using the scripts 5. **Generate .ics file** and deliver to user --- ## Step 1: Gather Information Ask the user for the following. They may provide some of this upfront; fill in what you have and ask for the rest. **Required:** - The scheduling order PDF (uploaded file) - Matter name (how the user wants it displayed on calendar entries, e.g., "Smith v. Jones Co.") - Proceeding type: **litigation** or **arbitration** **If litigation:** - Jurisdiction: **Try to determine from the scheduling order first.** Look for the court name, case number format, or header to identify the jurisdiction. Common patterns: - "District Court, ___ County, Colorado" → Colorado - "United States District Court" → Federal - "Superior Court of California" → California - State name in the
- Quick Start Workflow
- Step 1: Gather Information
- Step 2: Parse the Scheduling Order
- Step 3: Verify Rules Are Current
- Step 4: Compute Deadlines
- Optional Fields on Any Deadline Entry
- Step 5: Generate the .ics File
- Reference Files
- Calendar Entry Format
- Edge Cases and Warnings
python scripts/compute_deadlines.py --input /tmp/input.json --output /tmp/computed.json Outlook / Apple Calendar (default): python scripts/generate_ics.py --input /tmp/computed.json --output /path/to/output/[matter_name]_deadlines.ics Google Calendar: python scripts/generate_ics.py --input /tmp/computed.json --output /path/to/output/[matter_name]_deadlines.ics --google
What does the litigation-deadline-calendar skill do?
Calendar litigation and arbitration deadlines from a scheduling order. Parses a PDF scheduling order, identifies key dates, computes backward deadlines using the applicable rules (Colorado CRCP, Federal FRCP, or arbitration forum rules for AAA/JAMS), and generates an .ics calendar file for Outlook or Google Calendar import. Use this skill whenever the user mentions: litigation deadlines, scheduling order, case management order, deadline calendaring, discovery deadlines, trial preparation deadlines, arbitration scheduling, or anything related to computing or tracking court or arbitration deadli
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill litigation-deadline-calendar-dave-marcus --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.