Skip to main content

employee-handbooks

Use when writing or revising employee handbooks — covers content, plain language, legal review, and update cadence.

설치로 이동

소스 정보

저장소
ccashwell/agentic-hr
최근 소스 활동
2026년 4월 25일 23:49
감지된 SKILL.md 언어
영어
스타
0
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
employee-handbooks
description
Use when writing or revising employee handbooks — covers content, plain language, legal review, and update cadence.
# Employee Handbooks ## Core Frame A handbook is a living document used by employees and managers daily, not a legal CYA filed and forgotten. Plain language is the standard. Counsel review is mandatory for anything with legal implication. A bad handbook reads like a contract; nobody actually reads it; it contradicts how the company operates. ## What to Include Core sections for most companies: 1. **Welcome and purpose** — what this is, what it isn't 2. **Employment basics** — at-will (US), employment categories, classification (FLSA), I-9 3. **Compensation and benefits** — how comp works, pay periods, benefits overview, equity 4. **Time off and leave** — vacation/PTO, sick, parental, FMLA, bereavement, jury duty, military 5. **Workplace conduct** — anti-harassment, anti-discrimination, anti-retaliation; reporting channels 6. **Performance and development** — performance system overview, growth, learning resources 7. **Communication and IT** — acceptable use, monitoring (be honest), data handling, AI usage 8. **Health and safety** — workplace safety, accommodations process, mental health resources 9. **IP and confidentiality** — IP assignment, confidentiality, restrictive covenants (jurisdiction-specific) 10. **Separation** — resignation, termination, final pay, COBRA, references Strong legal caveat: jurisdictional variation is enormous. The above is general scaffolding; counsel must review for the specific jurisdictions where employees work. ## What to Leave Out - Policies that nobody enforces (better to remove than keep an unenforced rule) - Detailed procedures (those belong in SOPs) - Aspirational culture statements that contradict actual practice - Forced patriotism, ideological statements, anything that doesn't actually govern employment ## Plain Language Principles - **Active voice**: "We pay employees biweekly" not "Employees shall be compensated on a biweekly basis" - **Short sentences**: 15–20 words target - **Defined terms once**: don't define "employee" in every section - **Concrete examples**: "If you're sick, message your manager and take the day. You don't need a doctor's note unless you're out 3+ consecutive days." - **Acknowledge nuance**: "Some situations don't fit cleanly. When unsure, ask your manager or HR." ## Disclaimer Section (US) Most US handbooks include language clarifying: - Handbook does not create a contract - Employment is at-will (where applicable) - Handbook can be updated; employees notified - Specific written contracts (offer letters) supersede handbook in case of conflict This language is jurisdiction-specific; counsel drafts. ## Update Cadence - **Annual review**: confirm policies match practice; update for legal changes - **Triggered updates**: legislation changes, business changes (acquisition, expansion to new geo), incidents that surface gaps - **Sub-section updates**: as needed, with employee notification ## High-Stakes Policies (Counsel-Drafted) ### Anti-Harassment / EEO - Defined behaviors and examples - Reporting channels (multiple) - Anti-retaliation explicit - Investigation process described - Jurisdiction-aware (NY, CA mandatory training requirements) ### Accommodations - Interactive process described - Multiple ways to request - Privacy commitments - ADA-aware ### IP Assignment - Strong jurisdictional sensitivity (CA Labor Code 2870, etc.) - Often part of offer letter / separate IP agreement - Counsel-drafted ### Restrictive Covenants - Non-compete enforceability varies dramatically by state (CA prohibits; recent FTC activity) - Non-solicit and non-disclosure more commonly enforceable - Counsel-drafted ### Remote Work Policy - Eligibility (which roles, geographies) - Tax and registration implications (state nexus, international) - Equipment and expense - Performance expectations ### AI Usage Policy - Increasingly important - What's allowed (which tools, for what purposes) - Confidentiality (don't paste IP into public AI tools) - Disclosure requirements - Customer / client data handling ### Compensation Transparency - What's published internally - What's required externally (job posting ranges in CA, NY, CO, WA, MA, etc.) - Process for compensation questions ## Process for Writing or Revising 1. **Audit**: what exists today? What's missing? Outdated? 2. **Draft**: plain language; specific behaviors; clear accountabilities 3. **Counsel review**: jurisdiction-specific 4. **Leadership review**: does this reflect how we operate? 5. **Employee input** (where appropriate): test for comprehension 6. **Publish**: communicate clearly; make findable; track acknowledgment if required 7. **Operationalize**: managers and HR can apply 8. **Revise**: scheduled and as-needed; version-controlled ## Common Failures - Copy-paste handbook from another company - Legalese over plain language - Policies that contradict actual practice - Vague where specificity matters; strict where flexibility matters - No counsel review - Update neglect - Unenforced rules kept "just in case" - Aspirational language masquerading as policy ## Cross-References - `policy-writer` agent - `legal-and-jurisdictional-boundaries` rule - `hr-operations-architect` agent - `compensation-strategist` agent ## Key References - McCord, P. (2017). *Powerful*. - Industry templates from Justworks, Gusto, BambooHR (useful starting points; dangerous as final docs) - Counsel for jurisdictions where you operate (non-substitutable)
GitHub에서 보기