Reviewing an executive employment agreement template against a new state workplace fairness statute to produce a compliance memo and a redlined updated template.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill review-and-update-employment-agreement-template-for-new-state-labor-regulations --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Review And Update Employment Agreement Template For New State Labor Regulations?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-review-and-update-employment-agreement-template-fo)More formats (shields.io, HTML) on the badges page.
---
name: review-update-employment-agreement-template-state-regs
task_id: intellectual-property/review-and-update-employment-agreement-template-for-new-state-labor-regulations
description: Reviewing an executive employment agreement template against a new state workplace fairness statute to produce a compliance memo and a redlined updated template.
activates_for: [planner, solver, checker]
---
# Skill: Review and Update Employment Agreement Template for New State Labor Regulations
## 1. Subject-matter triage
- Start by isolating the new Illinois labor provisions that directly constrain executive employment terms, then map them to the template’s operative clauses.
- Treat the task as both an issue-spotting review and a drafting/redline exercise: the memo explains the compliance position; the redline implements it.
- If the source set includes internal policy, handbook language, arbitration policy, or offer-letter templates, check them alongside the agreement because a mismatch can make the template internally inconsistent even if the statutory text is satisfied.
- If only one state statute is in scope, say so explicitly; if multiple labor protections are implicated, enumerate them before analysis and address each separately.
## 2. Failure modes the skill is correcting
- Reviewing the template against the new statute without tying each statutory rule to the actual contract language it changes.
- Treating all problematic provisions as equally defective instead of separating void language from language that can be cured with a statutory carve-out or disclosure.
- Missing cross-document conflicts between the agreement, internal policy, and related onboarding materials.
- Producing only a memo or only a redline, rather than both required deliverables.
- Using vague comments like “revise for compliance” without identifying the legal rule, the affected clause, and the downstream effect on enforceability or risk.
- Leaving changes implicit in formatting only, which can be lost in export or review.
## 3. Legal frameworks / domain conventions that apply
- Apply the controlling Illinois statute and any specified implementing regulations or interpretive guidance for workplace fairness, plus any generally accepted employment-law doctrines needed to interpret the template.
- Review restrictions commonly found in executive employment agreements, including:
- mandatory arbitration of protected claims,
- confidentiality and nondisclosure limits,
- anti-retaliation and complaint-reporting protections,
- restrictive covenants such as non-compete and non-solicitation terms,
- choice-of-law and forum-selection provisions,
- severability and blue-pencil language,
- at-will and cause/termination language.
- For each legal proposition, cite the controlling authority by name and section in the memo and in any explanatory redline comment.
- Distinguish between:
- provisions that are unenforceable as written,
- provisions that remain permissible only if narrowed or carved out,
- provisions unaffected by the new statute.
- Preserve the agreement’s commercial structure unless the statute requires deletion or replacement; avoid overcorrecting clauses that can be fixed surgically.
- When a clause is affected by more than one rule, explain both rules and the interaction rather than describing only the most obvious one.
## 4. Analytical scaffolds
1. Identify every statutory requirement, prohibition, or safe harbor in the provided legislative materials that can affect the agreement.
2. Enumerate the affected contract topics before analysis if more than one is implicated.
3. For each topic, map the statute to the corresponding template section and classify the current language as:
- prohibited / unenforceable as written,
- permissible with revision,
- unaffected.
4. Check whether any related internal policy or companion document creates a conflict with the required revision.
5. Draft the fix in the least disruptive form that satisfies the statute: deletion, replacement, carve-out, savings clause, notice language, or conforming edit.
6. Test the revised clause against severability, forum, arbitration, and restrictive-covenant provisions to ensure the document still works as a whole.
7. If a clause is preserved, explain why it survives under the cited authority; if it is changed, explain why the revision is necessary.
8. For each issue entry in the memo, include:
- the affected clause,
- the controlling legal authority,
- the current status,
- the required revision,
- the practical consequence if left unchanged.
## 5. Vertical / structural / temporal relationships
- Read the agreement vertically: introductory provisions may affect later confidentiality, dispute resolution, and restrictive-covenant language.
- Track how amendments to one clause affect related definitions, remedies, governing law, and severability provisions.
- If the statute applies only to future conduct or future agreements, distinguish new hires, renewals, amendments, and existing signatories if the source materials provide that distinction.
- If timing matters, distinguish pre-signature drafting fixes, post-signature implementation issues, and any required notice or acknowledgment step.
- If the agreement uses defined terms that are reused across multiple clauses, update the defined term once and then confirm consistency everywhere it appears.
## 6. Output structure conventions
- Produce two deliverables: a compliance memo and a redlined updated template.
- Prepare the redlined template first as the operative document, then the memo after the revised language is settled.
- The redlined template must be reviewable from plain text as well as formatting: show every substantive change with explicit textual markup such as [DELETED: ...], [INSERTED: ...], or [REPLACED: old → new], and add a short [Rationale: ...] comment for each change.
- Do not rely on styling alone to signal edits.
- The compliance memo should be organized by statutory provision or issue category, and each entry should state:
- severity on a consistent ordinal scale defined once at the top,
- the affected agreement section,
- the controlling authority,
- whether the current language is void, must be narrowed, or is unaffected,
- the required revision,
- the consequence of leaving the clause unchanged.
- End the memo with a concise Recommended Actions block that assigns each action to a responsible role and ties it to the regulatory update or drafting milestone.
- Keep the redlined template internally consistent with the memo; every issue identified in the memo should correspond to an implemented change or an explicit decision not to change.
- Before finishing, confirm that both named deliverables are complete, non-empty, and contain the operative revisions rather than a description of them.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!