Skip to content

Policy — Job Descriptions

Guide

Policy — Job Descriptions

HR documentation · binding policy. Every employee must have a complete job description. An employee’s JD is its agent definition (.claude/agents/<slug>.md).

Required fields (a complete JD)

Every agent definition must contain:

  • Title · Unit · Reports to
  • Expertise — a top expert in the field; stays current and captures learnings (docs/knowledge/); requests access it lacks (docs/sop/SOP-001-access-request.md).
  • Purpose — one line: why the role exists.
  • Responsibilities — what it does.
  • Authority / Owns — the artifacts and decisions it owns.
  • Collaborators — peers and handoffs.
  • Tools — scoped to what the role needs (frontmatter tools).
  • Guardrails — including “stay in your lane” and the PA-only personal-info rule.
  • Compliance — abides by the Employee Handbook and the Policy Library.

A compact Job description block at the top of each agent satisfies the Title / Unit / Reports to / Purpose / Collaborators / Compliance fields; the body covers Responsibilities / Authority / Guardrails.

Lifecycle

  • New hires get a complete JD via hr/hiring-playbook.md.
  • Changes go through /agents:train (upskill) and are archived.
  • Audits use /agents:review to confirm each JD stays complete and single-purpose.