law-firm-ops

v1.0.0 MIT business updated 2026-09-27

Turn a new-client JSON object into a formatted intake summary Markdown file — client details, parties, matter type, facts, fee arrangement, a checkbox-style conflicts-check log to complete, and next steps. Use right after an initial consultation to document the matter and drive the follow-up sequence.

$ skillbank install law-firm-ops@1.0.0
# pins exactly 1.0.0 · README + changelog included

Law Firm Ops

Overview

The consultation ends, the prospect leaves, and then nothing happens — because nobody wrote the intake down. This skill takes a small JSON object with the client name, contact, matter type, opposing parties, facts summary, and fee arrangement, and writes a formatted intake-summary Markdown file. The summary includes a conflicts-check log: one checkbox row per party, so the firm can document the conflicts search before a file is ever opened.

Use it with the consultation follow-up playbook in references/consultation-followup.md: same-day thank-you with the engagement letter attached, day-3 check-in, and the day-10 nudge tied to a real deadline.

Installation

1. Copy the law-firm-ops/ directory anywhere convenient. 2. Make the script executable (Unix):


   chmod +x scripts/intake.py

No pip install needed — standard library only.

Configuration

Input is a JSON object with these fields:


{
  "client_name": "Harborview Apartments LLC",
  "contact": "Maria Santos — maria.santos@example.com, (555) 214-8890",
  "matter_type": "Landlord-tenant: commercial lease dispute",
  "opposing_parties": ["Breakwater Coffee Roasters Inc.", "James Okafor (personal guarantor)"],
  "facts_summary": "Tenant stopped paying rent in June 2026 ...",
  "fee_arrangement": "Hourly at $325/hour, $3,000 retainer ..."
}

All six fields are required; opposing_parties must be a JSON array of non-empty strings. Missing or malformed input prints a clear error to stderr and exits nonzero — never a traceback.

Inputs

| Command | Arguments | Returns | |-------------|----------------------------------|--------------------------------------| | intake.py | --in <json> --out <markdown> | Writes the intake summary Markdown file. |

No arguments prints usage to stderr and exits 2. --help prints usage and exits 0.

Worked example

Tested with a realistic landlord-tenant matter (one client, two opposing parties):


$ ./scripts/intake.py --in client.json --out intake-summary.md
Wrote intake summary for Harborview Apartments LLC to intake-summary.md

$ cat intake-summary.md
# Client Intake Summary

Prepared: 2026-09-27

## Client
- **Name:** Harborview Apartments LLC
- **Contact:** Maria Santos, property manager — maria.santos@example.com, (555) 214-8890

## Matter type
Landlord-tenant: commercial lease dispute over unpaid rent and alleged maintenance failures

## Parties
- **Client:** Harborview Apartments LLC
- **Opposing parties:**
- Breakwater Coffee Roasters Inc.
- James Okafor (personal guarantor)

## Facts summary
Tenant occupies Unit 3B under a 5-year commercial lease signed 2023-02-01 at $4,200/month. Tenant stopped paying rent in June 2026 and claims the landlord failed to repair the HVAC system and roof leak after written notice on 2026-04-12. Landlord states repairs were completed 2026-05-20 and has invoices. Three months of rent ($12,600) remain outstanding. No eviction action filed yet; client seeks advice on demand notice, possible eviction, and guarantor liability.

## Fee arrangement
Hourly at $325/hour, $3,000 retainer replenished at $1,500 balance; litigation expenses billed separately with prior approval.

## Conflicts-check log

Run every party above (and their known affiliates) through the firm's
conflicts database before engagement. Do not open a file until each row
below is filled in.

| Party | Relationship to matter | Searched in (list system) | Conflict found? | Date checked |
|-------|------------------------|---------------------------|-----------------|--------------|
| Harborview Apartments LLC |  |  | [ ] Yes  [ ] No |  |
| Breakwater Coffee Roasters Inc. |  |  | [ ] Yes  [ ] No |  |
| James Okafor (personal guarantor) |  |  | [ ] Yes  [ ] No |  |

## Next steps
- [ ] Conflicts check completed and documented above
- [ ] Engagement letter / fee agreement sent and signed
- [ ] Retainer received and deposited to trust account
- [ ] Initial matter file opened and calendar holds set

Safety notes

The script reads your client JSON and writes a local Markdown file — it never uploads or transmits anything. Intake summaries contain privileged client information: store them where your firm's confidentiality rules say they belong, and never paste client facts into a public AI service.

Version history

Changelog

1.0.0 — 2026-09-27

  • Initial public release.
  • scripts/intake.py: client JSON → formatted intake-summary Markdown file with parties, matter type, facts, fee arrangement, checkbox-style conflicts-check log, and next steps.
  • references/consultation-followup.md: same-day thank-you, day-3 check-in, day-10 engagement-letter nudge.
  • Zero dependencies; tested with a landlord-tenant sample (2 opposing parties) plus bad-input cases.

← back to catalog