chro-advisor
People leadership for scaling companies. Covers hiring strategy, compensation design, org structure, performance management, retention, culture health, and workforce planning. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building career ladders, handling attrition, workforce planning, or when user mentions CHRO, HR, people strategy, talent acquisition, headcount, compensation, org design, retention, performance management, employee engagement, or people operations.
What this skill does
# CHRO Advisor
People strategy and operational HR frameworks for business-aligned hiring, compensation, org design, performance management, and culture that scales. The CHRO translates business goals into people requirements and ensures the organization has the talent, structure, and culture to execute.
## Keywords
CHRO, chief people officer, 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, workforce planning, people analytics, eNPS, onboarding, offboarding, DEI, employer brand
---
## Quick Start
### Workforce Planning Decision Tree
```
START: Business goal identified
|
v
[Can existing team deliver this goal?]
|
+-- YES --> [Is current capacity sustainable?]
| |
| +-- YES --> No hiring needed. Optimize.
| +-- NO --> Hire for sustainability (backfill/support)
|
+-- NO --> [Is this a skill gap or capacity gap?]
|
+-- SKILL GAP --> [Can we develop internally in < 90 days?]
| |
| +-- YES --> Train/develop. No hire.
| +-- NO --> Hire specialist.
|
+-- CAPACITY GAP --> [Is this temporary or permanent?]
|
+-- TEMPORARY --> Contract/agency
+-- PERMANENT --> Full-time hire with business case
```
---
## Core Responsibilities
### 1. Workforce Planning and Headcount
Every hire needs a business case. "We need more people" is not a business case.
#### Hiring Justification Framework
| Question | Required Answer |
|----------|----------------|
| What revenue or risk does this role address? | Specific dollar amount or risk description |
| What happens if we don't fill this in 90 days? | Concrete impact statement |
| Can existing team absorb this with re-prioritization? | Yes/No with explanation |
| What's the fully-loaded cost (salary + benefits + equity + tools + overhead)? | Dollar amount |
| What's the expected ramp time to full productivity? | Weeks/months |
| Who will manage this person? | Named manager with capacity |
#### Headcount Planning by Stage
| Stage | Team Size | CHRO Focus | Hiring Speed |
|-------|-----------|------------|--------------|
| Pre-seed | 1-5 | Founders hire directly | 1-2/quarter |
| Seed | 5-15 | First structured interviews, no HR person yet | 2-4/quarter |
| Series A | 15-40 | First People hire, comp bands, career ladder v1 | 4-8/quarter |
| Series B | 40-100 | CHRO or VP People, full hiring process, HRIS | 8-20/quarter |
| Series C | 100-250 | People team (3-5), manager training, performance system | 15-40/quarter |
| Growth | 250+ | Full people function, analytics, L&D, total rewards | 30+/quarter |
### 2. Compensation Design
#### Compensation Band Architecture
```
Level Framework:
IC Track Management Track
--------- ----------------
L1: Junior/Associate --
L2: Mid-level --
L3: Senior M1: Manager (first-time)
L4: Staff/Principal M2: Senior Manager
L5: Distinguished/Fellow M3: Director
-- M4: VP
-- M5: SVP/C-level
```
#### Band Construction Method
| Step | Action | Data Source |
|------|--------|------------|
| 1 | Define levels with clear competency criteria | Internal role descriptions |
| 2 | Benchmark each level against market | Levels.fyi, Pave, Radford, Option Impact |
| 3 | Set band width (typically 20-30% spread) | Market data + internal equity |
| 4 | Position band midpoint at target percentile | P50 for cash, P50-P75 for total comp |
| 5 | Define equity bands per level | Stage-appropriate equity calculator |
| 6 | Set promotion criteria between levels | Performance + scope + impact |
#### Total Compensation Components
| Component | Purpose | Refresh Cadence |
|-----------|---------|-----------------|
| Base salary | Market-rate cash compensation | Annual review |
| Annual bonus | Performance-linked variable pay | Annual (if applicable) |
| Equity (options/RSUs) | Long-term alignment and retention | Initial grant + annual refresh |
| Benefits | Health, 401k, perks | Annual review |
| Signing bonus | Competitive offer sweetener | One-time |
#### Equity Grant Guidelines by Stage
| Stage | IC Hire (L2-L3) | Senior Hire (L4-L5) | VP/C-Level |
|-------|-----------------|---------------------|------------|
| Seed | 0.25-1.0% | 1.0-2.5% | 2.0-5.0% |
| Series A | 0.05-0.25% | 0.25-0.75% | 0.5-2.0% |
| Series B | 0.01-0.10% | 0.10-0.30% | 0.25-1.0% |
| Series C+ | 0.005-0.05% | 0.05-0.15% | 0.10-0.50% |
### 3. Organizational Design
#### Spans of Control Guidelines
| Role Type | Optimal Span | Warning Signs |
|-----------|-------------|---------------|
| IC Manager (engineering) | 5-8 direct reports | > 10: no coaching time. < 4: unnecessary layer |
| IC Manager (non-eng) | 6-10 direct reports | > 12: overwhelmed. < 5: manager inflation |
| Manager of Managers | 4-7 direct reports | > 8: can't support managers. < 3: too many layers |
| VP/Director | 5-8 direct reports | > 10: strategic thinking suffers |
#### When to Add Management Layers
```
TRIGGER: Team growing past threshold
|
v
[Current span of control > optimal?]
|
+-- NO --> Don't add layer. Resist the urge.
+-- YES --> [Is there a strong internal candidate?]
|
+-- YES --> Promote from within (faster, culture-preserving)
+-- NO --> [Is external hire justified?]
|
+-- YES --> Hire manager with 90-day expectations
+-- NO --> Split team instead of adding layer
```
#### Org Design Anti-Patterns
| Anti-Pattern | Symptom | Fix |
|-------------|---------|-----|
| Title inflation | Everyone is a "Head of" at 20 people | Standardized level framework |
| Shadow org | Real decisions made outside official structure | Align authority with accountability |
| Matrix chaos | Every person has 3 reporting lines | One clear manager, dotted lines documented |
| Founder bottleneck | All decisions flow through founder | Delegation framework (see `founder-coach`) |
| Empire building | Managers hire to grow team, not to deliver | Tie headcount to business outcomes |
### 4. Performance Management
#### Calibrated Performance Framework
| Rating | Label | Distribution Target | Action |
|--------|-------|---------------------|--------|
| 5 | Exceptional | 5-10% | Accelerated promotion, significant equity refresh, retention bonus |
| 4 | Exceeds Expectations | 20-25% | Above-market raise, stretch assignment, mentor role |
| 3 | Meets Expectations | 50-60% | Market adjustment, development plan, new challenges |
| 2 | Needs Improvement | 10-15% | PIP with 60-day milestones, weekly manager check-ins |
| 1 | Underperforming | 2-5% | Exit conversation or immediate role change |
#### Performance Review Cadence
| Activity | Frequency | Owner | Participants |
|----------|-----------|-------|-------------|
| 1:1 meetings | Weekly | Manager | Manager + direct report |
| Goal check-in | Monthly | Manager | Manager + direct report |
| Peer feedback collection | Quarterly | People team | Cross-functional peers |
| Performance review | Semi-annual | Manager + People | Manager, report, skip-level |
| Calibration session | Semi-annual | People team | All managers at same level |
| Promotion committee | Semi-annual | People + Leadership | Committee of L4+ leaders |
#### PIP (Performance Improvement Plan) Structure
| Element | Requirement |
|---------|-------------|
| Specific gaps | Observable behaviors, not vague criRelated 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.