People ops
Headcount Request Pack
Prepare evidence for a headcount decision.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Prepare evidence for a headcount decision.
What it covers
Inputs
Role/team, business need, start date, budget assumptions.
Result
Headcount request with business case, alternatives, cost assumptions and approval needs.
What it uses
People recordsCalendarEmailDocumentsSlackCRMRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Rippling, Google Workspace, Slack, Attio.
Procedure
- Call keep_status and report freshness for: Rippling, Google Workspace, Slack, Attio. If a required connector for Headcount Request Pack is disconnected or stale, say so up front.
- Resolve inputs for Headcount Request Pack: role, candidate, req_id, time_window. Default time window: open reqs and active interview loops (override if caller provides time_window). Ask only for missing critical inputs.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Headcount Request Pack (filter out unrelated day-plan noise).