/policy-drafting

1. Load ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint, handbook location.
2. Use the workflow below.
3. Draft core policy. Check each jurisdiction in footprint for required variants.
4. Output: core policy + state supplements. Flag where law is currently shifting.

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /employment-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/employment-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.

Purpose

A policy that's right for California may be wrong (or unnecessary) in Texas. This skill drafts a core policy and generates state supplements where the footprint requires different rules.

Load context

~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint, handbook location and format.

Workflow

Step 1: Scope the policy

• What's the policy for? (Remote work, parental leave, social media, etc.)
• Why now? (Legal requirement, incident, growth, gap noticed)
• Who does it apply to? (All employees, certain roles, certain locations)

Step 2: Jurisdictional scan

For each state/country in the footprint, check: does this jurisdiction have a specific rule on this topic?

Common topics with jurisdictional variance:

If the topic has no jurisdictional variance (dress code, say), skip this step.

Step 3: Draft the core policy

One policy. Applies everywhere. Clear and readable — employees should understand it without a lawyer.

Structure:

• Purpose (one sentence — why this policy exists)
• Scope (who it applies to)
• The rule (what's required/permitted/prohibited)
• Process (how to request, who approves, what happens if)
• Questions (who to ask)

Avoid: "heretofore," "notwithstanding," nested exceptions. This is a handbook policy, not a contract.

Step 4: State supplements

For each jurisdiction where the rule differs, a supplement:

### [State] Supplement

Employees working in [State] are subject to the following in addition to / instead of the core policy:

- [Specific difference]
- [Cite the state law if helpful]

Keep supplements tight. Only what's different — don't repeat the core.

Step 5: Cross-check

• Does this policy conflict with anything already in the handbook?
• Does it promise more than the company intends to deliver? (A policy is a promise — courts hold employers to handbook promises.)
• Does it inadvertently create a contract? (Some states treat handbook policies as contractual — include the standard "this is not a contract" language if the handbook doesn't already.)

Output

# [Policy Name]

## Core Policy

[Full text]

## State Supplements

### [State 1]
[Supplement]

### [State 2]
[Supplement]

---

## Drafting Notes (internal — remove before handbook insertion)

- **Jurisdictional scan:** [which states checked, which have variance]

…