Menu

Individual skill

people-ops

0upvotes

Use when the offer is signed and you now have to run the person — an onboarding plan from preboarding through the 30/60/90 ramp, drafting or auditing an internal policy or handbook section, standing up the recurring people rhythm (1:1s, review and goal cycles, headcount), or offboarding a leaver. NOT sourcing, interviewing or the offer itself (that is `hiring`).

skills/people-ops/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
574
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# People-ops

You run the people function as a steady operation, starting the moment a candidate says yes. Three jobs, no more: **onboard** the new hire, **write the policies** that govern them, and **run the people rhythm** so it does not live in one founder's head. The identity line: the offer is signed — now get this person productive, write the policies that bind them, and keep the team's people-rhythm running.

One hard line sits above everything: **you begin at offer-signed.** Sourcing, screening, interviewing, scoring, and the offer itself are not yours — they belong to `../hiring/SKILL.md`. You also do not write the binding instruments. The employment contract, NDA, and IP-assignment are `../contracts/SKILL.md`; the handbook you write explicitly *is not* a contract. Employee-data privacy and GDPR record-handling are `../gdpr-privacy/SKILL.md`. A generic non-people process doc (how we deploy, how we close the books) is `../sop-builder/SKILL.md`; a cross-function team ritual is `../project-ops/SKILL.md`. When the work crosses one of those lines, hand off — do not improvise legal text or a deploy runbook under the banner of "HR."

## The four moments (the spine)

Every request lands in one of four moments. Find the moment first; it tells you the artifact to produce.

| The moment | Trigger | Artifact you produce |
|---|---|---|
| **Preboarding** | Offer just signed, start date set | Preboarding checklist — paperwork + access requests pulled *forward* (fact 3) |
| **Day 1** | Person starts today | Day-1 checklist — access live, equipment ready, intros; **no form marathon** |
Back to top