Skip to main content
skill CX Codex official · Anthropic

matter-workspace · anthropics, product-legal — Claude Code skill: what it does, how to install

matter-workspace — a skill for Claude Code that isolates client matter context in private legal practice. It manages separate folders for each engagement so contexts never mix.

Apache-2.0 ★ 10,060 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add anthropics/claude-for-legal
/plugin install product-legal@claude-for-legal
Open on GitHub

What matter-workspace does

This skill creates and manages isolated directory workspaces for individual legal matters inside ~/.claude/plugins/config/claude-for-legal/product-legal/matters/.

Subcommands create workspaces (new), switch active clients (switch), list existing matters (list), archive them (close), or detach back to practice-level work (none). Running new triggers an intake interview to capture client details, counterparties, risk overrides, and files like matter.md and notes.md. Closed matters move into _archived/ and remain readable for conflicts checks.

The skill stays disabled by default for in-house teams. It requires private-practice mode or Enabled: ✓ in the practice-level CLAUDE.md to run.

What it helps with

  • isolate files and notes across multiple legal clients
  • create structured matter folders through an intake interview
  • switch the active matter context in CLAUDE.md
  • archive closed client engagements without deleting records

Example prompts for the agent

  • /product-legal:matter-workspace new acme-msa-2026
  • /product-legal:matter-workspace switch acme-msa-2026
  • /product-legal:matter-workspace list

How to install matter-workspace

1Plugin marketplace

/plugin marketplace add anthropics/claude-for-legal
/plugin install product-legal@claude-for-legal

This installs the whole product-legal plugin with all its skills

2Skills CLI (Vercel)

npx skills add anthropics/claude-for-legal --skill matter-workspace -a claude-code

3Manually: put the files in place

~/.claude/skills/matter-workspace/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/matter-workspace/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about matter-workspace

How to install matter-workspace in Claude Code?

Run /plugin marketplace add anthropics/claude-for-legal and then /plugin install product-legal@claude-for-legal.

What does matter-workspace do?

It isolates matter-specific notes, decisions, and context in separate folders so data from one engagement does not leak into another.

What is required for matter-workspace to work?

Matter workspaces must be enabled under ## Matter workspaces in the practice-level CLAUDE.md; by default, the feature is turned off for in-house setups.

Source text

SKILL.md · Apache-2.0
---
name: matter-workspace
description: >
  Manage matter workspaces — new, list, switch, close, or detach (practice-level).
  Use when working across multiple clients or matters in private practice and you
  need to create, list, switch, close, or detach the active matter so context from
  one engagement doesn't leak into another.
argument-hint: "<new | list | switch | close | none> [slug]"
---

# /matter-workspace

Practitioners work across multiple clients and matters. A matter workspace keeps one client or engagement's context separate from every other. This skill manages those workspaces.

## Subcommands

- `/product-legal:matter-workspace new <slug>` — create a new matter workspace, run a short intake, write `matter.md`
- `/product-legal:matter-workspace list` — list matters with status and active flag
- `/product-legal:matter-workspace switch <slug>` — set the active matter
- `/product-legal:matter-workspace close <slug>` — archive a matter (move to `~/.claude/plugins/config/claude-for-legal/product-legal/matters/_archived/`, never delete)
- `/product-legal:matter-workspace none` — detach from any active matter, work at practice-level only

## Instructions

1. Read `~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md` — confirm the `## Matter workspaces` section is populated. If `Enabled` is `✗`, tell the user: "Matter workspaces are off — you're configured as an in-house practice with one client, so the plugin works from practice-level context automatically. If you actually work across multiple clients, re-run `/product-legal:cold-start-interview --redo` and select a private-practice setting. Otherwise, you don't need `/matter-workspace` at all." Don't error — the disabled state is the expected one for in-house users.
2. Apply the storage layout and subcommand logic below.
3. Dispatch on the first token of `$ARGUMENTS`:
   - `new` → run the intake interview, write `~/.claude/plugins/config/claude-for-legal/product-legal/matters/<slug>/matter.md`, seed `history.md` and `notes.md`.
   - `list` → enumerate `~/.claude/plugins/config/claude-for-legal/product-legal/matters/*/matter.md`, print a table, mark the active matter.
   - `switch` → update the `Active matter:` line in the practice-level CLAUDE.md.
   - `close` → move `~/.claude/plugins/config/claude-for-legal/product-legal/matters/<slug>/` to `~/.claude/plugins/config/claude-for-legal/product-legal/matters/_archived/<slug>/`, log the close date in `history.md`.
   - `none` → set `Active matter:` to `none — practice-level context only`.
4. Show the user what changed and confirm before writing.

## Notes

- This skill never reads across matters unless `Cross-matter context` is `on` in the practice-level CLAUDE.md.
- Archiving is not deletion — closed matters remain readable for retention/conflicts purposes.
- Slugs are lowercase with hyphens. If a slug is reused across archived and active, the archived one is preserved under `_archived/<slug>/`.

---

# Matter Workspace

Multi-client practitioners (private practice — solo, small firm, large firm) work across many matters. Context from one must not leak into another. This skill is the thin file-management layer that makes that true.

**Default state is off.** In-house users never see this — they run at practice-level only. Matter workspaces turn on at cold-start for private-practice users, or by editing `## Matter workspaces` in the practice-level CLAUDE.md. If `Enabled` is `✗`, this skill does not run; the `/matter-workspace` command explains the disabled state and suggests `/cold-start-interview --redo` for users who actually need matter isolation.

## Storage layout

All matter data lives under:

```
~/.claude/plugins/config/claude-for-legal/product-legal/
├── CLAUDE.md                       # practice-level practice profile
└── matters/
    ├── <slug>/
    │   ├── matter.md               # client, counterparty, matter type, key facts, overrides
    │   ├── history.md              # dated log of events, decisions, drafts, reviews
    │   ├── notes.md                # free-form working notes
    │   └── outputs/                # skill outputs for this matter (optional subfolder)
    └── _archived/
        └── <slug>/                 # closed matters — readable but not active
```

Slugs are lowercase with hyphens. Examples: `acme-msa-2026`, `zenith-renewal`, `vendor-xyz-nda`.

## Active matter is in the practice CLAUDE.md

The `Active matter:` line under `## Matter workspaces` in the practice-level CLAUDE.md is the single source of truth. Switching a matter edits that line. No separate state file.

## Subcommand logic

### `new <slug>`

1. Confirm slug is not already present in `matters/<slug>/` or `matters/_archived/<slug>/`. If reused, ask the user to pick a different slug.
2. Run the intake interview:
   - **Client** (the party we represent, or the internal business unit if in-house)
   - **Counterparty** (the other side — may be multiple)
   - **Matter type** (read the plugin's practice profile for typical categories; for product-legal: launch | feature review | marketing claim review | risk deep dive | product area (standing) | other)
   - **Confidentiality level** (standard | heightened | clean-team — heightened prompts extra care in cross-matter settings)
   - **Key facts** (2–5 sentences: what this matter is about, who the stakeholders are, what's at stake)
   - **Matter-specific overrides to the practice playbook** (e.g., "client requires 24-month LoL cap not 12", "counterparty is a strategic partner — relationship-preserving tone")
   - **Related matters** (slugs of any connected matters)
3. Write `matters/<slug>/matter.md` using the template below.
4. Seed `matters/<slug>/history.md` with a single "Opened" entry.
5. Create an empty `matters/<slug>/notes.md`.
6. Do **not** auto-switch to the new matter. Ask: "Want to switch to `<slug>` now? (`/product-legal:matter-workspace switch <slug>`)"

### `list`

Enumerate `matters/*/matter.md`. Read each file's front-matter or first few lines to extract status. Print a table:

| Slug | Client | Matter type | Status | Opened | Active |
|---|---|---|---|---|---|

Mark the currently-active matter with `*`. Include `_archived/*` under a separate "Archived" heading if any exist.

### `switch <slug>`

1. Confirm `matters/<slug>/matter.md` exists. If not, offer `/product-legal:matter-workspace new <slug>`.
2. Edit the `Active matter:` line in the practice-level CLAUDE.md to `Active matter: <slug>`.
3. Show the user the matter.md summary so they can confirm they're on the right matter.

### `close <slug>`

1. Confirm `matters/<slug>/` exists.
2. Append a "Closed" entry to `matters/<slug>/history.md` with today's date.
3. Move `matters/<slug>/` → `matters/_archived/<slug>/`.
4. If the closed matter was the active matter, set `Active matter:` to `none — practice-level context only`.

### `none`

Set `Active matter:` in the practice-level CLAUDE.md to `none — practice-level context only`. Confirm with the user.

## `matter.md` template

```markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this` in the practice-level CLAUDE.md]

# Matter: [Client] — [short description]

**Slug:** [slug]
**Opened:** [YYYY-MM-DD]
**Status:** active
**Confidentiality:** [standard / heightened / clean-team]

---

## Parties

**Client:** [name]
**Counterparty:** [name(s)]

## Matter type

[vendor MSA | customer agreement | NDA | SaaS subscription | amendment | renewal | other — with one-line rationale]

## Key facts

[2–5 sentences. What this matter is about. Who the stakeholders are. What's at stake. What makes it different from the default playbook.]

## Matter-specific overrides

*Any deviation from the practice-level playbook that applies to this matter and only this matter.*

- [e.g., "LoL cap: client requires 24 months, not house standard 12."]
- [e.g., "Tone: relationship-preserving — counterparty is a strategic partner."]
- [e.g., "Governing law: must be English law, not Delaware."]

## Related matters

- [slug — one line why related]

## Notes on confidentiality

[If heightened or clean-team, describe why. Who may see matter files. Whether cross-matter context is permissible even if globally on.]
```

## `history.md` seed

```markdown
# History: [Client] — [short description]

Append-only event log. Most recent at top.

---

## [YYYY-MM-DD] — Matter opened

Intake completed. Slug: `[slug]`. Status: active.
[Any initial context worth preserving beyond matter.md — e.g., "Opened in response to inbound MSA draft from [counterparty]."]
```

## Cross-matter context

The practice-level CLAUDE.md has a `Cross-matter context:` flag. When it's `off` (the default), a skill working in matter A **never reads** files in `matters/B/` for any other `B`. Period. This is the confidentiality guarantee the setting exists to provide.

When it's `on`, a skill may read files across matter folders only when the user explicitly asks it to (e.g., "compare our position on liability caps across the last five vendor matters"). Even when `on`, the default is to load only the active matter unless the user asks for a cross-matter view.

## What this skill does not do

- **Run a conflicts check.** Conflicts are the practitioner's/firm's job; the intake captures what the user declares.
- **Enforce retention.** Closing archives a matter; it does not delete. Retention policy is out of scope.
- **Auto-route outputs.** The substantive skill decides where to write; this skill tells it *which folder* is active, not what to put in it.
- **Decide whether cross-matter is appropriate.** It reads the flag and obeys.

© Anthropic · Apache-2.0 · anthropics/claude-for-legal

Similar skills

All skills for Agent setup: memory, context, orchestration →

matter-workspace by other authors comes first.

matter-workspace official anthropics matter-workspace — a skill for Claude Code, Codex, Cursor, GitHub Copilot and other platforms that creates isolated workspaces for each matter or client. CX Codex +1 633installs matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for legal matters. Create a matter, switch the active context, list matters, or archive a closed one. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for client matters. It creates, lists, switches, and archives matters, or clears the active matter. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for legal matters. It creates, lists, switches, and archives matters, or detaches the active one. CX Codex +1 ★ 10,060repo stars matter-workspace official Anthropic The matter-workspace Claude Code skill manages separate workspaces for client matters. It creates and switches matters, lists them, and archives closed ones. CX Codex +1 ★ 10,060repo stars nx-workspace nrwl A skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that gives AI agents the commands to navigate an Nx workspace. CX Codex +1 100,600installs cargo-workspace-management getcargo cargo-workspace-management is a Claude Code skill that administers Cargo workspaces through the CLI, inviting teammates, managing API tokens and folders, and filing bug reports. CX Codex +1 11,600installs gsd-workspace open-gsd This Claude Code skill creates, lists, and removes isolated GSD workspaces. Use its flags to choose a workspace workflow. CX Codex +1 569installs postplus-workspace PostPlusAI postplus-workspace keeps one project folder holding approved product facts, campaign context and finished results, so repeated PostPlus work does not start from zero. CX Codex +1 360installs ae-workspace ThinkingAIAgenticEngine The ae-workspace Claude Code skill manages AgentSpaces through ae-cli. Requests to change members, capabilities, or files activate it. CX Codex +1 165installs saving-workspace-context spencerpauly The saving-workspace-context skill writes research, decisions and templates into your workspace files, so the next session starts with context instead of a blank slate. CX Codex +1 545installs

From the same set174

The whole set →
matter-workspace The matter-workspace Claude Code skill manages separate workspaces for legal matters. Create a matter, switch the active context, list matters, or archive a closed one. CX Codex +1 ★ 10,060repo stars customize The customize Claude Code skill edits individual settings in a regulatory practice profile. It runs when someone asks to change watched regulators, a threshold, or another profile section. CX Codex +1 ★ 10,060repo stars cold-start-interview cold-start-interview — a Claude Code skill that configures a regulatory watchlist, indexes policy files, and records a materiality threshold. Run it for initial setup, a reset, or an integration check. CX Codex +1 ★ 10,060repo stars reg-change-monitor The reg-change-monitor subagent for Claude Code and Codex monitors regulatory feeds for changes. It filters data by a materiality threshold, creating a concise digest to deliver only significant updates. CX Codex ★ 10,060repo stars customize The customize Claude Code skill edits a product counsel practice profile one section at a time. It activates when someone asks to update a profile, risk calibration, or review framework. CX Codex +1 ★ 10,060repo stars cold-start-interview The cold-start-interview Claude Code skill builds a product counsel profile from past launch reviews and connected services. Run it for initial setup, counsel onboarding, or a fresh risk calibration. CX Codex +1 ★ 10,060repo stars launch-watcher Claude Code subagent launch-watcher monitors upcoming releases in Jira or Linear and flags tasks requiring legal review. CX Codex ★ 10,060repo stars use-case-triage The use-case-triage Claude Code skill classifies data processing as needing a PIA, a mandatory DPIA, or no assessment. It runs on privacy questions about a new feature, activity, or vendor relationship. CX Codex +1 ★ 10,060repo stars

Project sponsors

Companies that keep this analytics open