Team Leave and Holiday Coverage Planner
--- name: team-leave-and-holiday-coverage-planner description: Plans team leave around minimum staffing, especially over the holidays - checks every workday against role coverage rules (one person fills one slot)…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
--- name: team-leave-and-holiday-coverage-planner 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. --- # Team Leave and Holiday Coverage Planner 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. ## Files in this skill - `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) - `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 - `references/fair-leave-policy.md` - priority rules, blackout periods, allowance and carry-over, how to say no well, and what each finding code means - `templates/leave-plan-brief.md` - the plan to send to the team - `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 - `examples/support-leave.csv` - 3 approved and 7 requested leaves, including a half day - `examples/support-plan.md` - the real planner output on those files ## Workflow ### 1. Collect the inputs 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". ### 2. Run the planner ``` python3 scripts/leave_cover.py examples/support-team.json examples/support-leave.csv python3 scripts/leave_cover.py team.json leave.csv --json python3 scripts/leave_cover.py --self-test ``` 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. ### 3. Read the result - 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. - Allowance problems (LV02): approved leave over the allowance needs HR to confirm carry-over or unpaid days. - Requests: approve the ones marked approve; for conflicts and blackouts take the alternative to the person, not a refusal (LV04). - Fairness (LV05) and peak days off: check nobody gets the best days two years running while someone who worked them is refused. - Fragility: roles with no spare (LV03) and days with zero slack (LV07) need a named backup. - Use-it-or-lose-it (LV06): people who will lose days should book them in quiet weeks. ### 4. Adjust and re-run 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. ### 5. Deliver 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. ## Example result 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. ## Rules - Check coverage by role with one person per slot, not by headcount alone. - Apply one stated priority rule to everyone and show the order; never decide by who asked loudest. - Always pair a "not this time" with an alternative date, a shorter trip or a…
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Fix LaTeX dollars
PromptsInvestigate and fix the actual $ usages in Markdown content. The $ fall into three classes: - Currency (escape these) — $1, $2 billion, R$ 549 → these pairs cause all the warnings - Real math (leave alone) —…
-
{ "role": "Approval Processor", "context": "You are responsible for processing annual leave requests.", "task": "Calculate and adjust annual leave balance when form_id is 1.", "constraints": [ "Oly apply to form_nid…
-
--- name: building-a-comprehensive-programming-team description: Create a programming team with defined roles: team brain, task distributor, programmer, and manager, ensuring a well-rounded and effective development…
-
A cinematic, magical Halloween neighborhood street decorated for a festive autumn celebration. Glowing carved Jack o lanterns line the pathways and steps of cozy suburban houses. Vibrant autumn leaves in shades of…
-
7v7 Football Team Generator App
PromptsAct as an Application Designer. You are tasked with creating a Windows application for generating balanced 7v7 football teams. The application will: - Allow input of player names and their strengths. - Include fixed…
-
Minecraft image
PromptsI want to make a ultra realistic minecraf character out of an image, the character should have all the characteristics of the person in the eg. Skin color and outfit leave out the background intact the finished result…