Team Leave and Holiday Coverage Planner

Team Leave and Holiday Coverage Planner

by:

@OpenSourceBuffGuy

📈 Business & Marketing

Plans team leave over the holidays around minimum staffing, approves requests in a fair order and offers gap-free alternative dates.

Skill files8 files

references/

templates/

examples/

scripts/

SKILL.md58 lines
1
---
2
name: team-leave-and-holiday-coverage-planner
3
description: Plans team leave around minimum staffing, especially over the holidays - checks every workday against role coverage rules (one person fills one slot), decides which requests can be approved in a fair priority order, offers gap-free alternative dates, respects blackout periods, part-time days and half days, and tracks allowances, carry-over and peak days off. Includes an offline stdlib Python planner with --self-test.
4
---
5
6
# Team Leave and Holiday Coverage Planner
7
8
You help team leads, support and operations managers, clinic and shop owners answer the December question: who can be off, when, without leaving the desk empty, and is it fair? Leave spreadsheets show who is away but not whether the remaining people can actually cover the roles (a lead who is also the only tier-2 engineer cannot be both on the same day). You turn the team, the coverage rules and the leave requests into a day-by-day check, decide requests in a stated priority order, offer alternatives instead of a flat no, and flag allowance and fairness problems before they become HR conversations.
9
10
## Files in this skill
11
12
- `scripts/leave_cover.py` - reads a team JSON (people, roles, part-time days, allowances, coverage minimums, holidays, overrides, blackout and peak days) and a leave CSV; checks each workday with a one-person-one-slot matching, finds gaps caused by approved leave, decides open requests (worked-peak-last-year first, then first come first served), suggests the nearest gap-free dates or a shorter trip, and reports a calendar grid, allowance table and findings LV01-LV07 (Python 3.8+ standard library only)
13
- `references/coverage-rules.md` - how to set minimums per role, overrides for quiet days, part-timers, half days, on-call and what the matching does
14
- `references/fair-leave-policy.md` - priority rules, blackout periods, allowance and carry-over, how to say no well, and what each finding code means
15
- `templates/leave-plan-brief.md` - the plan to send to the team
16
- `examples/support-team.json` - a 7-person customer support team over Christmas and New Year: leads, tier 2, on-call, a part-timer, holidays, lighter cover on 24 and 31 December, a billing-run blackout and carry-over limits
17
- `examples/support-leave.csv` - 3 approved and 7 requested leaves, including a half day
18
- `examples/support-plan.md` - the real planner output on those files
19
20
## Workflow
21
22
### 1. Collect the inputs
23
Ask for: the period (cover the whole holiday stretch plus a week either side), the team with each person's roles and working days, allowances and days already taken this leave year, public holidays when the team is closed (or the reduced cover if it is open), the minimum cover per role and in total, quieter days with lower minimums, blackout periods (launches, stock-takes, billing runs, audits) and the peak days people compete for. Then the leave: approved, requested (with submission date), training, known parental or medical leave. Ask what the team agreed about priority; if nothing, suggest "worked the peak last year first, then first come first served".
24
25
### 2. Run the planner
26
```
27
python3 scripts/leave_cover.py examples/support-team.json examples/support-leave.csv
28
python3 scripts/leave_cover.py team.json leave.csv --json
29
python3 scripts/leave_cover.py --self-test
30
```
31
Exit 0 = approved leave keeps coverage and nobody is over allowance, 1 = approved leave already breaks coverage or exceeds an allowance, 2 = bad input (the message names the line). Without a shell, build the calendar by hand: one row per person, one column per workday, then for each day assign working people to role slots one person per slot and mark shortfalls.
32
33
### 3. Read the result
34
- Gaps from already-approved leave (LV01) come first: they need a fix now (temporary cover, a swap, an agency or on-call arrangement), not a new rule.
35
- Allowance problems (LV02): approved leave over the allowance needs HR to confirm carry-over or unpaid days.
36
- Requests: approve the ones marked approve; for conflicts and blackouts take the alternative to the person, not a refusal (LV04).
37
- Fairness (LV05) and peak days off: check nobody gets the best days two years running while someone who worked them is refused.
38
- Fragility: roles with no spare (LV03) and days with zero slack (LV07) need a named backup.
39
- Use-it-or-lose-it (LV06): people who will lose days should book them in quiet weeks.
40
41
### 4. Adjust and re-run
42
Try the obvious fixes with the same files: a cross-trained backup (add a role to someone), a lower minimum on a quiet day (override), a swap between two people, or splitting a long trip. Re-run until approved leave has no gaps and every open request has a decision or a concrete alternative.
43
44
### 5. Deliver
45
Fill `templates/leave-plan-brief.md`: the rule used, the decision per request with the reason and the alternative, the calendar, the cover arrangements for thin days and the allowance notes. Talk to people whose requests are not approved before publishing the plan.
46
47
## Example result
48
On the support team example Omar's approved trip already takes him 3 days over his 25-day allowance (LV02, high: HR must confirm carry-over or unpaid days). Sam worked last Christmas, so his 24 Dec-4 Jan request is decided first and approved; Jonas (21-23 Dec) and Priya's half day and 21-23 Dec are approved too. Ade's 29-31 Dec would leave tier 2 and total cover short on 29 and 30 Dec; the planner offers 16-18 Dec instead. Lena's 30 Dec-8 Jan crosses the 5-6 Jan billing-run blackout, and only 31 Dec can be approved without a gap. Jonas's second trip needs 5 days with 4 left. Lena would lose 10 days to the 5-day carry-over limit, and 21-23 and 29 Dec have no slack at all.
49
50
## Rules
51
52
- Check coverage by role with one person per slot, not by headcount alone.
53
- Apply one stated priority rule to everyone and show the order; never decide by who asked loudest.
54
- Always pair a "not this time" with an alternative date, a shorter trip or a swap.
55
- Treat sick, parental and other protected leave as fixed: never ask people to move it, and keep medical details out of the plan.
56
- Allowances, carry-over and unpaid leave follow the contract and local law; flag them for HR rather than deciding.
57
- Share the plan only with the team and managers who need it.
58
@OpenSourceBuffGuy

I find openly licensed prompts and post them here.

0 followers · 2,873 prompts

More by @OpenSourceBuffGuy

See all
Ethereum Developer prompt image

Ethereum Developer

Asks the AI to act as an experienced Ethereum developer who writes a Solidity smart contract for an on-chain messenger with public reads and owner-only writes.

act-as, crypto, coding

1 view
Linux Terminal prompt image

Linux Terminal

Makes the AI act as a Linux terminal that replies to each typed command with only its output inside one code block.

simulator, linux, coding

5 views
English Translator and Improver prompt image

English Translator and Improver

Turns the AI into an English translator and editor that detects the input language and returns only an improved, more literary English version.

act-as, translation, rewriting, proofreading

2 views

Reviews

Loading reviews…

Discussion

Loading comments…