本文へ移動
cccskills
無料GitHub で公開

policy-drafting

Draft an employment policy with state supplements where law differs across the jurisdictional footprint. Use when the user says "draft a [topic] policy", "we need a policy on", "update our [topic] policy", or names a policy gap.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/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:

TopicVariance
Paid leaveState mandates (CA, NY, CO, WA, etc.) with different accrual rates, uses, carryover
Parental leaveState programs layer on top of FMLA (CA PFL, NY PFL, etc.)
Meal and rest breaksCA is the outlier (penalty pay); most states minimal
Expense reimbursementCA requires; most states don't
Pay transparencyGrowing list of states requiring ranges in postings
Non-competesSee hiring-review skill — unenforceable in some states
Final payTiming varies widely

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]
- **Conflicts with existing handbook:** [none | list]
- **Law currently shifting:** [any state where this is in flux]
- **Review cadence:** [when to revisit — annual, or when X happens]

Draft, not a policy in effect. This is a drafting aid for attorney review, not a policy you can publish. Publishing a handbook policy has legal consequences — in several states it can bind the company as a contractual promise, and wage/leave/accommodation policies are routinely read against the employer. A licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction reviews, edits as needed, and takes professional responsibility before the policy is rolled out. Do not publish or distribute this draft unreviewed.

Handoff

To handbook-updates skill: when this policy is approved, it diffs against the current handbook and flags what changes.

What this skill does not do

  • Approve the policy. It drafts; a human approves.
  • Roll out the policy. Communication to employees is an HR workflow.
  • Cover every jurisdiction on earth — only the ones in the footprint. If the footprint expands, re-run.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

Detects when Luminance, Kira, or a similar bulk-review tool is in use, hands off the high-volume clause extraction to it, and QAs its output per the trust level in `~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md`. Use when user says "send to Luminance", "bulk review", "AI extraction", or when diligence-issue-extraction hits a high-volume category.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

Bar prep questions — MBE or essay, targeted at your weak subjects and bar jurisdiction. Tracks misses and comes back to patterns. Use when the user says "bar prep", "MBE questions", "practice essay", or "test me for the bar".

日本語の概要は準備中です。原文の説明を表示しています。

anthropics/claude-for-legal9,6542026年9月30日 更新

anthropics のスキルをすべて見る

このスキルの問題を報告する