Pace
All teams / People

People

Recruiting, onboarding, performance, compensation, policy.

People ops is high-volume across recruiting, onboarding, performance reviews, comp, and policy work. Each one has a repeatable shape and a personalized layer. Pace handles the repeatable parts so you spend more time on the personalized ones. `onboarding-plan` personalizes a 30-day plan by role; saves hours per hire.

Install for People

The full people starter set is 3 plugins. Pick the install path that matches you.

Cowork (no terminal)

Click each link below; Cowork opens and asks you to confirm. Restart Cowork after the last one so connectors register.

  1. 1 Install human-resources
  2. 2 Install productivity
  3. 3 Install enterprise-search
After the last install, restart Cowork. The MCP servers (Slack, HubSpot, etc.) only register cleanly on a fresh app start. Quit the app fully, then reopen it.

Terminal (one command)

If you have claude on your PATH already, this installs the whole set in one go.

npx pace-tools install human-resources productivity enterprise-search

pace-tools wraps claude plugin install; runs claude plugin marketplace add GoldenBerry-SO/Pace automatically if you haven't registered the marketplace yet.

Plugins to install

Pick from this set for the role. Primary plugins are essential; companions multiply value.

  • human-resources primary

    Recruiting, onboarding, performance reviews, compensation analysis, policy lookup.

    claude plugin install human-resources@pace
  • productivity companion

    Manager workflows: 1:1 prep, calendar sanity, comms.

    claude plugin install productivity@pace
  • enterprise-search companion

    Policy lookups and precedent across docs.

    claude plugin install enterprise-search@pace

Connectors to set up

Claude prompts to authorize each one the first time a relevant skill fires. You only do this once per project.

  • Slack
  • Notion
  • Microsoft 365

Workflows

Common ways teams use these plugins day to day. Each one is a starting point; adapt the prompt to your context.

  • Job description

    Writes a JD tied to your leveling and comp band. Reads existing JDs from the same family for consistency.

    Write a job description for a senior backend engineer, band 3.

  • Onboarding plan

    Generates a personalized 30/60/90-day plan by role. Includes intros, reading list, first projects.

    Build the first-30-days onboarding plan for the new hire.

  • Performance review feedback

    Consolidates 360-degree feedback into themes, surfaces patterns, drafts the review.

    Consolidate the 360-review inputs for this person into a coherent summary.

  • Compensation analysis

    Compares a band against market data, flags compression risks, suggests adjustments.

    Run a comp analysis on the band-3 engineering population. Market median, internal distribution, outliers.

  • Policy lookup

    Answers a policy question by reading the connected docs.

    What is our parental leave policy? Pull the current one from the handbook.

Just say it

You don't have to memorize slash commands. After installing, type natural sentences into Claude and the right skill will fire. Each row is a real example.

  • You say

    Walk me through this week's recruiting funnel

    Claude triggers recruiting-pipeline
  • You say

    Prep me to interview Jane for the staff role

    Claude triggers interview-prep
  • You say

    Draft the offer letter for Jane at L5

    Claude triggers draft-offer
  • You say

    Help me write Maria's performance review

    Claude triggers performance-review
  • You say

    Plan headcount for the engineering org next quarter

    Claude triggers org-planning
  • You say

    Look up our PTO policy for new parents

    Claude triggers policy-lookup

Tips & tricks

Field-tested patterns from teams that have already shipped a quarter or two on these plugins.

  • Onboarding plans personalize

    `onboarding-plan` adapts by role. Hours saved per hire compound across teams.

  • Connect Notion early

    Most policy lookups live in Notion. Connector first, then /policy-lookup actually finds answers.

  • Use review-feedback for patterns

    Eyeballing 360s misses patterns; `review-feedback` surfaces them.

  • Comp analysis isn't a decision

    Treat the output as a starting point for the comp conversation, not the answer.

  • Pair with /enterprise-search

    For "did we already write something about X?" questions, the search plugin is faster than scrolling Slack.

  • JDs as a template family

    After three JDs for similar roles, build a /pace router command that wraps `job-description` with your leveling defaults.

See also