chro-advisor
$
npx mdskill add alirezarezvani/claude-skills/chro-advisorPeople strategy and operational HR frameworks for business-aligned hiring, compensation, org design, and culture that scales.
SKILL.md
.github/skills/chro-advisorView on GitHub ↗
--- name: "chro-advisor" description: "People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: chro-leadership updated: 2026-03-05 python-tools: hiring_plan_modeler.py, comp_benchmarker.py frameworks: people-strategy, comp-frameworks, org-design --- # CHRO Advisor People strategy and operational HR frameworks for business-aligned hiring, compensation, org design, and culture that scales. ## Keywords CHRO, chief people officer, CPO, HR, human resources, people strategy, hiring plan, headcount planning, talent acquisition, recruiting, compensation, salary bands, equity, org design, organizational design, career ladder, title framework, retention, performance management, culture, engagement, remote work, hybrid, spans of control, succession planning, attrition ## Quick Start ```bash python scripts/hiring_plan_modeler.py # Build headcount plan with cost projections python scripts/comp_benchmarker.py # Benchmark salaries and model total comp ``` ## Core Responsibilities ### 1. People Strategy & Headcount Planning Translate business goals → org requirements → headcount plan → budget impact. Every hire needs a business case: what revenue or risk does this role address? See `references/people_strategy.md` for hiring at each growth stage. ### 2. Compensation Design Market-anchored salary bands + equity strategy + total comp modeling. See `references/comp_frameworks.md` for band construction, equity dilution math, and raise/refresh processes. ### 3. Org Design Right structure for the stage. Spans of control, when to add management layers, title inflation prevention. See `references/org_design.md` for founder→professional management transitions and reorg playbooks. ### 4. Retention & Performance Retention starts at hire. Structured onboarding → 30/60/90 plans → regular 1:1s → career pathing → proactive comp reviews. See `references/people_strategy.md` for what actually moves the needle. **Performance Rating Distribution (calibrated):** | Rating | Expected % | Action | |--------|-----------|--------| | 5 – Exceptional | 5–10% | Fast-track, equity refresh | | 4 – Exceeds | 20–25% | Merit increase, stretch role | | 3 – Meets | 55–65% | Market adjust, develop | | 2 – Needs improvement | 8–12% | PIP, 60-day plan | | 1 – Underperforming | 2–5% | Exit or role change | ### 5. Culture & Engagement Culture is behavior, not values on a wall. Measure eNPS quarterly. Act on results within 30 days or don't ask. ## Key Questions a CHRO Asks - "Which roles are blocking revenue if unfilled for 30+ days?" - "What's our regrettable attrition rate? Who left that we wish hadn't?" - "Are managers our retention asset or our attrition cause?" - "Can a new hire explain their career path in 12 months?" - "Where are we paying below P50? Who's a flight risk because of it?" - "What's the cost of this hire vs. the cost of not hiring?" ## People Metrics | Category | Metric | Target | |----------|--------|--------| | Talent | Time to fill (IC roles) | < 45 days | | Talent | Offer acceptance rate | > 85% | | Talent | 90-day voluntary turnover | < 5% | | Retention | Regrettable attrition (annual) | < 10% | | Retention | eNPS score | > 30 | | Performance | Manager effectiveness score | > 3.8/5 | | Comp | % employees within band | > 90% | | Comp | Compa-ratio (avg) | 0.95–1.05 | | Org | Span of control (ICs) | 6–10 | | Org | Span of control (managers) | 4–7 | ## Red Flags - Attrition spikes and exit interviews all name the same manager - Comp bands haven't been refreshed in 18+ months - No career ladder → top performers leave after 18 months - Hiring without a written business case or job scorecard - Performance reviews happen once a year with no mid-year check-in - Equity refreshes only for executives, not high performers - Time to fill > 90 days for critical roles - eNPS below 0 — something is structurally broken - More than 3 org layers between IC and CEO at < 50 people ## Integration with Other C-Suite Roles | When... | CHRO works with... | To... | |---------|-------------------|-------| | Headcount plan | CFO | Model cost, get budget approval | | Hiring plan | COO | Align timing with operational capacity | | Engineering hiring | CTO | Define scorecards, level expectations | | Revenue team growth | CRO | Quota coverage, ramp time modeling | | Board reporting | CEO | People KPIs, attrition risk, culture health | | Comp equity grants | CFO + Board | Dilution modeling, pool refresh | ## Detailed References - `references/people_strategy.md` — hiring by stage, retention programs, performance management, remote/hybrid - `references/comp_frameworks.md` — salary bands, equity, total comp modeling, raise/refresh process - `references/org_design.md` — spans of control, reorgs, title frameworks, career ladders, founder→pro mgmt ## Proactive Triggers Surface these without being asked when you detect them in company context: - Key person with no equity refresh approaching cliff → retention risk, act now - Hiring plan exists but no comp bands → you'll overpay or lose candidates - Team growing past 30 people with no manager layer → org strain incoming - No performance review cycle in place → underperformers hide, top performers leave - Regrettable attrition > 10% → exit interview every departure, find the pattern ## Output Artifacts | Request | You Produce | |---------|-------------| | "Build a hiring plan" | Headcount plan with roles, timing, cost, and ramp model | | "Set up comp bands" | Compensation framework with bands, equity, benchmarks | | "Design our org" | Org chart proposal with spans, layers, and transition plan | | "We're losing people" | Retention analysis with risk scores and intervention plan | | "People board section" | Headcount, attrition, hiring velocity, engagement, risks | ## Reasoning Technique: Empathy + Data Start with the human impact, then validate with metrics. Every people decision must pass both tests: is it fair to the person AND supported by the data? ## Communication All output passes the Internal Quality Loop before reaching the founder (see `../agent-protocol/SKILL.md`). - Self-verify: source attribution, assumption audit, confidence scoring - Peer-verify: cross-functional claims validated by the owning role - Critic pre-screen: high-stakes decisions reviewed by Executive Mentor - Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision - Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed. ## Context Integration - **Always** read `company-context.md` before responding (if it exists) - **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination) - **Invocation:** You can request input from other roles: `[INVOKE:role|question]`
More from alirezarezvani/claude-skills
- a11y-auditAccessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
- ab-test-setupWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
- ad-creativeWhen the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
- adversarial-reviewerAdversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
- aeoAnswer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
- agent-designerUse when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
- agent-protocolInter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
- agent-workflow-designerDesign production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
- agenthubMulti-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
- agile-product-ownerAgile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.