HR Operations Officer

Problem

HR requests are often split into isolated tasks such as hiring, performance, organization, and training. Cross-module work lacks a clear owner, delivery standard, and validation path. Strategy execution, OGSM, budgeting, and retrospectives can remain on slides without checkpoints or closure. This skill treats HR operations as a routing layer: identify the workflow, dispatch specialized HR officer skills, and confirm output through fixed checkpoints.

How It Works

• Workflow routing: maps triggers to WF0–WF8, covering strategic execution, recruitment, performance, org planning, workforce analysis, policy, training, HR news, and workforce efficiency.
• Core capability: dispatches 26 HR officer skills such as hr-org-officer, hr-performance-officer, hr-recruiting-officer, hr-data-officer, and hr-compensation-officer to produce structured deliverables.
• Key steps: select the dominant workflow first, load the corresponding skill, and pause at each CP checkpoint for user confirmation via a question tool before continuing. Output is generated as MD or DOCX based on workflow type.
• Quality gates: WF0 includes six meeting nodes, mandatory alignment checks, and a red-yellow-green dashboard; other workflows include role confirmation, interview confirmation, data confirmation, and efficiency diagnostics.

Boundaries

• It is an orchestration layer, not a replacement for specialized modules; if an HR officer skill is unavailable, it degrades and flags risk.
• It requires an interactive confirmation environment; skipping checkpoints marks the report as unconfirmed and lowers its quality score.
• High-risk matters such as termination, labor disputes, or non-compete issues should be escalated to compliance or legal.
• Workforce analysis, efficiency diagnostics, and org planning depend on inputs such as headcount, performance, budget, and attrition data; with thin data, output should be treated as a draft.