Use when the user asks whether staffing covers demand across the business, names a hiring target, or hands over workload and team numbers: company-wide headcount planning with scenarios, not support shift scheduling.
Instructions your experts follow when using this skill.
Use this when the user asks whether staffing covers demand, names a hiring target, or hands over workload and team numbers. This is the business-wide plan — demand per function, required heads, the hiring plan, and the scenarios. Interval-level contact forecasting, shift schedules, and intra-day moves for a support desk belong to the workforce planning skill, not here.
Past demand by function and period, current heads and roles, shrinkage drivers (time off, training, attrition), open requisitions, and the forecast horizon.
No demand history means a judgment forecast marked INFERENCE with the data need named. No shrinkage figure means you plan at 20% and say so.
Forecast from history, never from headcount totals alone. Name the trend, the seasonality, and the known events — launches, renewals, holidays. Include pipeline-weighted demand, tentative work, and time off. State the horizon and the miss band plainly.
The 12-to-16-week horizon is what drives the hire, contract, or reskill call.
Required heads = base workload heads / (1 - shrinkage/100), where shrinkage covers time off, training, and attrition.
Show the math in one block so the capacity owner can check it. Call out the convention when overtime or contractors fill the gap instead of heads.
Heads on hand, open requisitions with start dates, and the shortfall per function and month. Name coverage gaps, never hide them.
Base and high demand. Each carries hiring targets, start-by dates, cost per hire beyond salary (benefits, onboarding time, tools, and time to full productivity), and what breaks if hires slip a month.
Before opening any role externally, check whether an existing team member can step in. Hold a per-function skills inventory beside the plan: current skills against required, the top two gaps, and whether each gap closes by hire, train, or contractor. Name every single-point-of-failure role.
Forecast against actual demand, hires landed against plan, utilization, and the one planning fix for next month. Log the forecast and the hires made.
Never present a guessed headcount as modeled. Never move requisition dates or headcount budgets without the capacity owner's yes.
Save the capacity plan under capacity, dated, with its scenarios.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.