new-workspace

name	new-workspace
description	Provision a new legal or investigative workspace on disk. Use when the user wants to start a case, evidence bundle, OSINT investigation, or document-review workspace. Accepts a workspace name and optional variant (legal-research | evidence-management | osint-investigation | document-analysis). Scaffolds the workspace, personalises CLAUDE.md from the user's global memory, and (by default) creates a GitHub repo.
disable-model-invocation	true
allowed-tools	Bash(mkdir *), Bash(cp *), Bash(cat *), Bash(git init *), Bash(git add *), Bash(git commit *), Bash(gh repo create *), Bash(gh auth status), Bash(git push *), Read

Provision Legal / Investigative Workspace

Creates a new workspace for a legal or investigative matter. This plugin's primitives (/legal-investigative:log-evidence, /legal-investigative:analyze-document, /legal-investigative:redact-content, /legal-investigative:generate-brief) are globally available once installed — this skill only provisions the data scaffold (CLAUDE.md, context/, research/, evidence/, etc.) that those commands read from and write to.

Arguments

$ARGUMENTS is parsed as:

• First positional: workspace name (kebab-case, used as directory and GitHub repo name). Required.
• Second positional (optional): target parent path. Defaults to ~/repos/github/my-repos.
• --variant=<legal-research|evidence-management|osint-investigation|document-analysis> (optional): which scaffold to copy. Default: legal-research.
• --jurisdiction=<code> (optional): jurisdiction hint for legal-research variant. israel loads the Israel sub-variant. Any other value is written as free-text into the workspace CLAUDE.md.
• --local-only (optional): skip GitHub repo creation and push. Default: create a public GitHub repo and push.
• --private (optional): create the GitHub repo as private. Default: public.

Examples

/legal-investigative:new-workspace tenancy-dispute
/legal-investigative:new-workspace small-claims-isr --variant=legal-research --jurisdiction=israel
/legal-investigative:new-workspace product-liability-evidence --variant=evidence-management
/legal-investigative:new-workspace subject-x-osint --variant=osint-investigation --private
/legal-investigative:new-workspace nda-review --variant=document-analysis --local-only

Procedure

1. Parse arguments

Extract workspace name, target parent path, variant, jurisdiction, and flags from $ARGUMENTS. If workspace name is missing, ask the user for it before proceeding. Default variant is legal-research.

2. Resolve the scaffold path

The bundled scaffold lives at ${CLAUDE_SKILL_DIR}/../../template/<variant>/. Confirm it exists. Valid variants: legal-research, evidence-management, osint-investigation, document-analysis.

If --variant=legal-research --jurisdiction=israel, also plan to overlay ${CLAUDE_SKILL_DIR}/../../template/legal-research/israel-variant/ on top of the base scaffold after the copy in step 4.

3. Read ambient facts

Read ~/.claude/CLAUDE.md if it exists. Extract OS, locale, timezone, and user identity facts. These will personalise the workspace's CLAUDE.md at step 5.

4. Create the workspace directory

mkdir -p <target-parent>/<workspace-name>
cp -r ${CLAUDE_SKILL_DIR}/../../template/<variant>/. <target-parent>/<workspace-name>/

If the Israel sub-variant applies, additionally:

cp -r ${CLAUDE_SKILL_DIR}/../../template/legal-research/israel-variant/. <target-parent>/<workspace-name>/

The sub-variant overlay replaces the base CLAUDE.md with the Israel-specific one and adds jurisdiction context files. Do not include the israel-variant/ folder itself inside the provisioned workspace — only its contents. Do not copy any .claude/ tree.

5. Personalise CLAUDE.md

Open the new workspace's CLAUDE.md and:

• Replace any placeholder identity with the facts from step 3.
• Add a short header noting the workspace name and variant (and jurisdiction for legal-research).
• If ambient facts include OS/locale/timezone, embed them so downstream commands can skip re-asking.

6. Prompt for workspace-specific facts

Ask the user only for facts this plugin can't infer. Write each into the new workspace's CLAUDE.md as a labelled line so commands can parse them:

• legal-research: matter name, jurisdiction (if not already set by --jurisdiction), parties, confidentiality level. Write as MATTER, JURISDICTION, PARTIES, CONFIDENTIALITY.
• evidence-management: case reference, hashing algorithms required (default sha256), whether OpenTimestamps / GPG signing is in use. Write as CASE_REF, HASH_ALGOS, OTS_ENABLED, GPG_SIGN.
• osint-investigation: subject / target descriptor, scope statement, legal/ethical boundaries. Write as SUBJECT, SCOPE, BOUNDARIES.
• document-analysis: document corpus description, governing jurisdiction if any, confidentiality level. Write as CORPUS, JURISDICTION, CONFIDENTIALITY.

7. Initialise git and (optionally) publish

cd <target-parent>/<workspace-name>
git init
git add .
git commit -m "Initial workspace from legal-investigative plugin"

Unless --local-only is set:

gh repo create <workspace-name> --<public|private> --source=. --push

If --private is passed, use --private; otherwise default to --public.

8. Next-step hints

After provisioning, print a short summary telling the user which primitives are relevant to the variant:

• legal-research → /legal-investigative:analyze-document, /legal-investigative:generate-brief
• evidence-management → /legal-investigative:log-evidence, /legal-investigative:generate-brief
• osint-investigation → /legal-investigative:analyze-document, /legal-investigative:generate-brief
• document-analysis → /legal-investigative:analyze-document, /legal-investigative:redact-content

Remind the user that /legal-investigative:redact-content is available in any variant when sensitive disclosure is required.