chro-advisor
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.
What this skill does
# 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]`
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.