infometa Handbook Updates
Matter context
Matter context. Check ## Matter workspaces in the practice-level practice-profile.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 ~/.codebuddy/plugins/config/legal-workflows/employment-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
Handbook changes have ripple effects. Change the PTO policy and you've affected the final pay calculation, the leave policy cross-reference, and three state supplements. This skill finds the ripples before they become inconsistencies.
Load context
~/.codebuddy/plugins/config/legal-workflows/employment-legal/practice-profile.md → handbook location, state supplements list, update cadence.
Workflow
Step 1: Get the change
- What section is changing?
- What's the new language?
- Why? (Legal requirement, policy decision, cleanup)
Step 2: Diff against current
Read the current handbook section. Show the diff:
- [old language]
+ [new language]
Step 3: Find cross-references
Search the handbook for references to the changed section:
- Other policies that cite this one ("see the PTO policy for accrual rates")
- Defined terms that this section uses or defines
- State supplements that modify this section
Each cross-reference: does it still make sense after the change? Flag any that break.
Step 4: State supplement impact
For each state supplement in ~/.codebuddy/plugins/config/legal-workflows/employment-legal/practice-profile.md:
- Does this supplement modify the section being changed?
- Does the change make the supplement obsolete, wrong, or incomplete?
- Does the change create a need for a new supplement in a state that didn't need one before?
Step 5: Promise check
Is the change reducing something the old version promised?
If yes: that's a risk. Some states treat handbook policies as contractual. Reducing a benefit may need more than just updating the document — advance notice, consideration, or in some cases it can't be done retroactively.
Flag this. Don't block it — but flag it.
Output
## Handbook Update: [Section name]
### Change
[diff]
### Cross-reference impact
| Section | References changed section | Still accurate? | Fix needed |
|---|---|---|---|
| [name] | [how] | ✅/⚠️ | [what] |
### State supplement impact
| State | Current supplement | After change | Action |
|---|---|---|---|
| [state] | [what it says] | [still valid / obsolete / needs update] | [none / update / new supplement needed] |
### Promise check
[If reducing a benefit: flag + jurisdictional risk note]
### Ready to publish
- [ ] Cross-references updated
- [ ] State supplements updated
- [ ] [If benefit reduction: notice/consideration addressed]
- [ ] Version number and date updated
- [ ] Acknowledgment process (if required)
What this skill does not do
- Approve handbook changes. HR/legal leadership does.
- Communicate changes to employees.
- Track acknowledgments.