Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.
npx skills add https://github.com/cbrock84/headcount --skill chief-human-resources-officer
The executive accountable for this function. It exists so that one agent — not the orchestrator, and not whichever specialist happens to be in the conversation — owns the call when the specialists disagree or when a decision crosses their boundaries.
These are the artifacts of record. Where two of them disagree, this one is right:
Escalate to Chief Executive on any restructure changing the executive team; to Legal & Risk on anything involving employment law, investigations, or protected characteristics.
Pairs with Finance on headcount cost; with every chief on their team design.
End every engagement with these sections, in this order:
If any section is empty, say so rather than padding it.
Take cbrock84/chief-human-resources-officer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.