opencode-for-legal/upstream/legal-clinic/client-comms/_README.md
alpha nerd 27fbe1f313
port to Opencode: 140 skills, 14 agents, 19 MCP configs
Port claude-for-legal plugin collection to Opencode skills format.

Changes:
- 140 skills ported to opencode-for-legal/skills/ (namespaced naming)
- 14 agents converted to Opencode subagent format
- 5 managed-agent cookbooks flattened to single agents
- 19 MCP servers converted to opencode.json format
- 11 practice-profile templates ported (CLAUDE.md → PROFILE.md)
- Remote skill catalog (index.json) for Opencode URL discovery
- Setup wizard skill for first-time configuration

License compliance:
- Original source preserved in upstream/ per Apache 2.0 §4(b)
- NOTICE.md documents derivative work and upstream attribution
- LICENSE copied into port directory
- README rewritten with port disclaimer and trademark notice

Platform updates:
- Removed all Claude Code/Cowork product-specific references
- Config paths updated to ~/.config/opencode/opencode-for-legal/
- Command syntax: /plugin:skill → opencode auto-loading
- Agent frontmatter converted (tools: → mode: subagent)
2026-06-13 15:15:53 +02:00

2.3 KiB

client-comms/ — per-case communication logs

One folder per case. Inside, a running log.md tracking every client contact — incoming and outgoing, across phone, email, text, letter, and in-person meetings. Produced and appended by /legal-clinic:client-comms-log.

Layout

client-comms/
├── _README.md                     # this file
└── [case-id]/
    └── log.md                     # append-only running log

Slug

Match the case's ID used elsewhere (intake record, deadlines.yaml case_id). One case = one folder.

Why this exists

  • Malpractice defense — "we communicated X on date Y" needs a record.
  • Continuity at handoff — the incoming student can read the log and know the client's story without re-interviewing.
  • Pattern visibility — five voicemails unreturned over six weeks is a supervision flag.
  • Client file-retention — law school clinics have retention obligations; this is part of the complete file.

What the log entries look like

## [YYYY-MM-DD HH:MM] — [in / out] — [medium]

**Who (student):** [name]
**Who (client side):** [client name, or third-party if call from opposing counsel/etc]
**Duration / length:** [10 min call | 3-paragraph email | 2-page letter]

**Summary:**
[What happened, 2-4 sentences. Substance plus tone where it matters.]

**Action items:**
- [Item the student owes the client, with deadline]
- [Item the client owes the student, with expected timing]

**Follow-up due:** [date if applicable]

**Notes:**
[Anything that matters but doesn't fit above — language used, family dynamic observed, client anxiety level]

What this folder does NOT contain

  • Substantive case analysis (that's in the intake / memo / status files)
  • Drafts of documents (those are in separate case folders)
  • Privileged attorney-only notes (those stay in whatever the clinic uses for internal case notes)

The comms log is factual record of contact, not legal work product. Keep substance in the log; keep strategy and analysis elsewhere.

Retention

Append-only. Never edit past entries — if something was wrong or needs clarification, add a new entry referencing the old one. The record of what was said and when is part of the client file; rewriting history defeats the purpose.