agentleFS
emtcmcaemtcmca/claude-for-legal-billing/skills/wip-review/SKILL.md

wip-review

Skill1 starsChanged 4 months agoMITView on GitHub

Review, edit, and approve pending time entries before invoicing — the pre-billing step. Use when preparing to send an invoice, doing end-of-month billing review, writing down or writing off entries, or auditing unbilled WIP across matters.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. sebGilR/ai-dev-workflow★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. About 0 are common, 9 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ~/.claude/plugins/config/claude-for-legal/billing/CLAUDE.md.

    line 25
  2. Very specific:

    If no arguments, default to: entries for the currently active matter's client (same detection logic as /billing-legal:billing-status).

    line 35
  3. Very specific:

    Read [billing_data_path]/time-register.yaml.

    line 39
  4. Distinctive:

    Read the register through the validator, not by hand: Run:

    line 41
  5. Distinctive:

    Do not recompute them and do not carry figures forward from earlier in the conversation.

    line 49
  6. Very specific:

    If scripts/register-read.ps1 is not present, this is an install predating it.

    line 56
  7. Very specific:

    If no entries match: "No pending entries found for [scope].

    line 61
  8. Distinctive:

    After displaying the table, show:

    line 94
  9. Very specific:

    After writing: "✓ [N] entries approved — ready for invoice generation via /billing-legal:invoice-generate [client-slug]."

    line 112
  10. Distinctive:

    Ask: "Write down to what? (Enter new hours, or enter a dollar amount)"

    line 133
  11. Distinctive:

    If hours: recalculate amount at the existing rate.

    line 134
  12. Distinctive:

    If dollar amount: recalculate hours at the existing rate (for records).

    line 135
  13. Very specific:

    Ask for a write-down note (stored in notes field): "Reason for write-down: (required)"

    line 137
  14. Distinctive:

    Ask: "Write-off reason: (required — e.g., 'Client relationship', 'Billing error', 'Included in flat fee')"

    line 148
  15. Very specific:

    Do not restate the original figures inside notes.

    line 153
  16. Distinctive:

    Ask which field to change: narrative, task code, activity code, date, attorney, hours, rate.

    line 158
  17. Very specific:

    Do NOT offer session_minutes_actual for editing.

    line 166
  18. Very specific:

    When the attorney types d (done) or has finished acting on entries, show a summary:

    line 175
  19. Distinctive:

    Delete entries — entries are never deleted.

    line 193

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/billing-legal:wip-review

When this runs

Attorney is preparing to invoice a client (or doing a general billing audit) and needs to review, approve, write down, or write off pending entries.

Instructions

Preflight - read /billing-legal:billing-guardrails first. It carries the approval gate, the append-only record rule, UTBMS field discipline, and the boundary on what this plugin records rather than decides. Where it conflicts with the steps below, the stricter rule wins.

1. Read config

Read ~/.claude/plugins/config/claude-for-legal/billing/CLAUDE.md. Get billing_data_path. Check for placeholders.

2. Determine scope

Parse $ARGUMENTS:

  • --client <slug>: show only entries for that client
  • --attorney <slug>: show only entries for that attorney
  • --matter <slug>: show only entries for that matter slug
  • --all: show all pending and approved entries across all clients and attorneys

If no arguments, default to: entries for the currently active matter's client (same detection logic as /billing-legal:billing-status). If no active matter, show all pending entries.

3. Load entries

Read [billing_data_path]/time-register.yaml. Filter to entries with status: pending or status: approved matching the scope.

Read the register through the validator, not by hand. Run:

powershell -NoProfile -NonInteractive -File "[billing_data_path]/scripts/register-read.ps1" -Client [client-slug]

It resolves the data path from config, confirms the register exists, parses every entry, checks that each amount equals hours x rate, and emits JSON with per-status totals. Use its numbers. Do not recompute them and do not carry figures forward from earlier in the conversation.

  • Exit 2: the register is absent. Stop, report the path it printed, write nothing.
  • Exit 3: it parsed but failed an invariant. Show the errors array and stop before any write. A register whose arithmetic does not hold has been edited by something other than this plugin.
  • Exit 4: config missing or still holds placeholders. Direct to /billing-legal:cold-start-interview.

If scripts/register-read.ps1 is not present, this is an install predating it. Say so, then fall back to reading the file directly under the rule below.

If time-register.yaml does not exist, STOP. Say: "No time register at [billing_data_path]/time-register.yaml. That file is absent, not empty -- billing data may be unsynced, the data path may be wrong, or the file may have been moved. I am not going to report figures I cannot read." Do not create it, do not proceed with zeroes, and do not answer from earlier in the conversation. Absent is a different condition from empty or comment-only, which is the normal state of a fresh install.

If no entries match: "No pending entries found for [scope]. Run /billing-legal:time-entry to add entries, or check a different scope."

4. Display the WIP table

Show the entries in a clean table, grouped by client, then by matter, then sorted by date:

## WIP Review — [Client Name]  (filter: [scope])

**Total pending: [N] entries  |  [Nh]  |  $[total]**

### [Matter slug] — [Matter description if known]

| # | Date | Attorney | Hrs | Rate | Amount | Code | Narrative | Status |
|---|---|---|---|---|---|---|---|---|
| 1 | 2026-05-21 | Alice Jones | 0.8h | $350 | $280 | L200 | Reviewed vendor MSA redline... | pending |
| 2 | 2026-05-23 | Alice Jones | 0.4h | $350 | $140 | L200 | Call with client re: counterparty... | pending |

**Subtotal: 1.2h — $420**

---

### [Next matter or "No matter assigned"]

...

---

**Grand total: [Nh] — $[total]**

5. Action menu

After displaying the table, show:

What would you like to do?
  a  Approve all pending entries
  [N]  Act on entry #[N] (approve, write down, write off, edit)
  d  Done — exit review

Wait for input.


Action: Approve all

Set all pending entries in scope to approved. Confirm the count before writing:

Approve [N] entries totaling [Nh] / $[total]? [Y/n]

After writing: "✓ [N] entries approved — ready for invoice generation via /billing-legal:invoice-generate [client-slug]."


Action: Act on entry #N

Show the full entry and offer:

Entry #[N]:  [date]  [attorney]  [hours]h  $[amount]  [narrative]

  a  Approve — move to approved
  w  Write down — reduce hours or amount
  x  Write off — zero out (write-off, not billed)
  e  Edit — correct narrative, task code, activity code, date, or attorney
  b  Back

Approve: Set status: approved. Show updated table row.

Write down:

  • Ask: "Write down to what? (Enter new hours, or enter a dollar amount)"
  • If hours: recalculate amount at the existing rate.
  • If dollar amount: recalculate hours at the existing rate (for records).
  • Show the change: [original] → [new]
  • Ask for a write-down note (stored in notes field): "Reason for write-down: (required)"
  • Before overwriting hours and amount, copy them to original_hours and original_amount if those are still null. Never overwrite an existing original_* value — a second write-down reduces from the already-reduced figure, and the original stays the first billed figure.
  • Confirm and write. Set status: approved after write-down.

The reason belongs in notes as prose. The figures do not. LINE_ITEM_ADJUSTMENT_AMOUNT in a LEDES export is computed from original_amount - amount, so a write-down whose original survives only inside a sentence exports as a zero adjustment and the client never sees the discount.

Write off:

  • Ask: "Write-off reason: (required — e.g., 'Client relationship', 'Billing error', 'Included in flat fee')"
  • Copy hours and amount to original_hours and original_amount first if those are still null. The size of what was absorbed is the substance of a write-off; a record that says only "zero" does not show the firm what it gave away.
  • Then set hours: 0, amount: 0.00, status: write-off, notes: "[reason] - written off [date]".
  • Do not restate the original figures inside notes. They live in original_hours and original_amount, where a report can total them.
  • Confirm before writing. Written-off entries remain in the register for records but never appear on invoices.

Edit:

  • Ask which field to change: narrative, task code, activity code, date, attorney, hours, rate.
  • For hours/rate: warn that changing these on an approved entry requires a write-down note.
  • For narrative: no restriction — corrections to descriptions are routine.
  • For activity code: offer the same A-series reference /billing-legal:time-entry uses, and write to activity_code. Entries logged before the field existed carry null, and this is the only way to set one — an entry with a null activity_code exports with an empty LINE_ITEM_ACTIVITY_CODE, which some e-billing platforms reject. Never write an A-code into task_code to work around it.
  • Do NOT offer session_minutes_actual for editing. It records what the attorney actually entered at capture time; a value typed in later is a reconstruction, not a measurement, and its whole purpose is supporting the round-up if a client's auditor asks.
  • Show the change and confirm before writing.

6. Exit

When the attorney types d (done) or has finished acting on entries, show a summary:

## WIP Review Summary

Approved:   [N] entries  [Nh]  $[total]
Written down: [N] entries  (reduced by $[amount])
Written off:  [N] entries  (removed $[amount])
Still pending: [N] entries

Ready to invoice: [N] entries for [Client(s)] — run `/billing-legal:invoice-generate [client-slug]`

What this skill does not do

  • Generate invoices — use /billing-legal:invoice-generate
  • Delete entries — entries are never deleted; write-off is the closest equivalent
  • Handle entries that are already billed — those are closed; contact billing counsel if a billed entry needs correction

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.