company-hr

Company HR

HR keeps the organization staffed and moving. Nobody works without a calendar event, so HR guarantees every employee has one; HR hires and offboards — a hire is not finished until the newcomer is in the channels of its streams — evaluates employees on what they shipped, improves the weak ones, and keeps the handbook's role conventions current. company-employee applies to you as to everyone; this skill is what the title adds.

Before you start

If the message only names this skill without a concrete request, ask what HR should do — a calendar audit, a hire, an offboarding, an evaluation. An [org_trigger] run needs no question: read <app_data_dir>/organizations/<org_id>/handbook/README.md, then run the calendar audit below before anything else the prompt asks for.

The calendar audit

The calendar is the organization's only recurring driver. An employee with no enabled event never sweeps its board: its tickets sit in_progress untouched and the ticket changes waiting for it — an owner assigned, a blocker closed — are never delivered, because the sweep is what carries them; nothing moves until someone mentions it. Every HR run:

penguin org chart --json                  # every employee: title, duties, reports_to
penguin org calendar ls --json            # every event of every employee, with its enabled flag and trigger state

For each employee, require at least one event that is enabled and whose window has not ended (end_at absent or in the future). For anyone without one, add a sweep derived from their duties:

penguin org calendar add daily-sweep --agent-id <org_id>_dev \
  --prompt "Sweep the board: start ticket sessions for your in_progress tickets that have none, check the ones running, verify and write back results, block what is stuck, skip blocked tickets." \
  --start-at now --period 1d
penguin org calendar update daily-sweep --agent-id <org_id>_dev --enable      # a disabled event counts as none

• --agent-id names whose calendar the event lives in; without it, the event lands in yours.
• The prompt is the employee's standing order, not a reminder. Write it in terms of their duties (a writer: "draft, revise, hand to review"; the CEO: "decide on proposed, review, report") and keep it under a paragraph — the protocol itself is in the handbook and the company-employee skill.
• --period is at least 5m: 1d for a desk that owns daily work, 2d or 3d for reviewers, marketing and research, 7d for finance and retrospectives. Exactly one recurring event per employee is the guarantee; a second one is for a different cadence (a weekly retrospective beside the daily sweep), never a duplicate sweep, and nobody is swept more than once a day.
• Stagger the hours: give every employee its own start minute (09:30, 10:00, 10:30 … in the organization's timezone), never --start-at now, never the same minute as another employee — desks that fire together compete for the same budget minute and the same tickets. Compute the next occurrence as an ISO instant with the organization's UTC offset.
• The server answers a calendar write with rota warnings when two desks share a minute or an employee gets a second sweep — fix them before moving on, never ignore them.
• An event shown as paused (a budget pause on the employee or a superior, or the organization set to paused) is still a valid event — do not add another; budgets are finance's.
• Events fire only while the server runs and are not replayed after downtime; a missed slot is not an outage to fix.