Day-to-Day Operating Flow

Track 1

Manager

Demetrio · runs the portfolio from the Hub

Stand up the Hub project one-time per client

/setup-firm-hub (Mode B)

+ New Cowork project named "Origin Firm Hub" - connect it to the Origin SharePoint folder - run /setup-firm-hub once to seed the Hub config (CLAUDE.md + HUB-origin.md) into that folder. Cowork projects can't be shared, so every team member creates their own Hub project pointed at the same SharePoint folder; the config loads from there. Plus, once, admin: add a second org owner.

Daily portfolio brief

/firm-brief

Open the Hub project. It loads the Hub config from the connected SharePoint folder (/hub-session-start), then lists all 121 matters sorted by urgency: overdue, due today, due this week, on hold, $ outstanding. Open the relevant matter to act on urgents.

New matter intake

/intake-batch · /setup-matter

/intake-batch - weekly Excel batch from the Hub, Phase 1 dry-runs; type approved to execute. /setup-matter - single new matter, ad hoc.

Visual portfolio

/tracker-dashboard

Click-through view across the whole portfolio. Run from the Hub when you need it.

Loop daily

Track 2

Operator Lawyer

Steady-state matter work · any lawyer (incl. the Manager when acting on a matter)

Open one matter

The matter folder, opened as its own Cowork project. Not the Hub. (Your own project - the SharePoint folder is what's shared, not the project shell.)

First time on this matter? Run /setup-matter before continuing.

Orient on the matter

/session-start

12-line brief: stage, last session, next action, deadlines flagged URGENT/APPROACHING, $ outstanding. Under two minutes. Marks the matter as in-use; if a colleague has it open, you get a "Sarah opened this 38 min ago - proceed anyway?" warning (overridable; stale marks auto-expire).

Do the work

/create-lod-origin · /court-forms

/pleadings · /special-paths

Drafts land in the matter's Drafts subfolder with a dated/versioned filename, so a re-run never overwrites an earlier draft. Documents move out only on explicit approved.

Mid-session checkpoint

/session-checkpoint

Run before /compact (or before auto-compact fires) on long sessions. Saves matter context to memory so the next /session-start picks up cleanly.

Close the session

/session-close

Refreshes MATTER-STATUS.txt (won't blind-overwrite a newer one a colleague wrote in the meantime - it warns and asks), clears the in-use mark. Picked up by the Manager's next /firm-brief automatically.

Loop per matter

Track 3

New Lawyer (joining)

e.g. Sarah, Day 1 · absorbing the existing system

First login one-time

Confirm the Origin SharePoint library is synced to your machine via the OneDrive client (hard prerequisite - everything reads/writes there)

Receive plugin push from the org plugin marketplace: firm.zip + matter.zip (or upload them; /setup-profile ships inside firm.zip)

Run /setup-profile in any project - Claude interviews you, generates your personalised profile, shows you where to paste it

Stand up your own Hub project one-time per client

+ New Cowork project named "Origin Firm Hub" - connect it to the Origin SharePoint folder - done. The Hub config loads from that folder automatically; nothing to paste or attach, no one to ask for "access". Skip this if you only work matters and never need the portfolio view.

Open first matter

Open the matter folder as its own Cowork project. Run /setup-matter (first time only), then /session-start. Same brief as the Operator.

↓ merges into Track 2 (Operator) ↓

How the tracks talk to each other

Operator's /session-close writes MATTER-STATUS.txt - Manager's next-day /firm-brief picks it up automatically. No status reports, no chasing.

Manager's /intake-batch or /setup-matter creates matter folders in SharePoint - any lawyer opens one as a Cowork project and runs /session-start. New Lawyer's first /session-close lands in the Manager's brief next morning, part of the system from Day 1. The shared layer is always the SharePoint files - Cowork projects are per-person local shells, nothing load-bearing in them.