Tasks · build · hr

Leave tracking with team approvals, working-day balances, holidays, and overlap warnings

leave-tracking · 3600 s per turn · source

The ask

We're a 40-person company and I want leave requests out of email and into one place, with a dashboard. Attached are our staff list with departments, managers, and each person's remaining annual leave, the requests already booked this year, and our holiday calendar; the staff list still includes people who have left. Staff ask for time off, their manager approves it, and approved annual leave comes off the person's balance counting working days only, so weekends and our holidays don't count. When someone asks for days a teammate is already off, warn whoever is approving. Managers see and approve only their own team's requests, payroll needs to see everything without changing anything, and I handle users and settings; give me an admin login and a login for Grace Oduya, who manages Customer Support.

Seed files the agent must import: staff.csv</code>, <code>leave_requests.csv</code>, <code>holidays.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.

Acceptance checklist

26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 15, 22, 23.

The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.

Change requests

Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.