| name | matter-journal |
| title | Matter Journal |
| description | Manages client matter journals — persistent case files that give Claude full context on every client and matter. Use this skill when the user says "new client", "new matter", "I'm working on [X]", "open the [X] matter", "update the journal", "log this", "what's the status of", "close the [X] matter", "set up", "configure", or mentions creating a new matter or asks about a client by name. Also use when the user asks "what am I working on", wants to review active matters, or dictates notes after a call or meeting. This is a context management skill — it creates, loads, and logs to journals. It does not draft documents, send emails, or perform legal analysis, but it provides the context that makes those tasks dramatically better. |
| author | bstevescherer |
| author_url | https://github.com/bstevescherer/heycounsel-community/tree/main/skills/matter-journal |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | general |
| language | en |
Matter Journal
You manage a system of per-matter journals — one markdown file per client
matter that accumulates everything Claude learns about that matter over
time. The journal is a living case file: a header identifying the matter
and a chronological log of everything that happened.
The journal makes you a better collaborator on every legal task because
you carry forward full context — strategy, client preferences, opposing
counsel behavior, negotiation history, deadlines, impressions — across
sessions. The richer the journal, the better you perform.
Architecture
Legal Matters/ ← the folder the attorney opened
├── CLAUDE.md ← standing instructions (written during setup)
├── matters.json ← index of all matters (auto-maintained)
├── Chen-Trademark-2026/
│ └── journal.md
├── Smith-BreachOfContract-2026/
│ └── journal.md
matters.json is the index. Each entry has: id, folder, client,
matter_name, matter_type, aliases, parties (role-tagged), status,
created, last_session. Aliases and parties enable fuzzy matching when
the attorney mentions a name.
First-Run Setup
If matters.json does not exist at the folder root, the system hasn't
been set up yet. This also triggers on "set up", "configure", "first time",
or any setup-related request.
- Explain briefly what you're about to create: "I'll create two files —
matters.json to track your matters, and CLAUDE.md so I automatically
load the right case file when you mention a client. Over time I'll build
up context on every matter so you never have to re-explain anything."
- Wait for approval. On confirmation:
- Read
references/claude-md-template.md and write its contents to
CLAUDE.md at the folder root
- Create
matters.json containing []
- Confirm: "Done. Want to create your first matter?"
Keep this conversational and quick. The attorney should never leave the
chat to set things up.
Create Matter
Triggered by "new matter", "new client", or any indication the attorney
wants to open a new case file.
Do not run a structured interview. Extract what the attorney already
said — client name, matter type, description, any parties mentioned. If
the client name or matter type is genuinely missing, ask for just those
in a single question.
Then ask one thing: "Do you have any existing files or notes on this?
Drop them and I'll start the journal from there. Or if you have an
existing folder, I can add the journal there."
Three paths:
