Skip to content

An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.

Coverage QC against public occupational taxonomies (#12)

Chris Brock4a2c1338fd4d
diff --git a/.claude/agents/it-operations.md b/.claude/agents/it-operations.md
index be677f7..cbe05c6 100644
--- a/.claude/agents/it-operations.md
+++ b/.claude/agents/it-operations.md
@@ -17,7 +17,7 @@ Reads: anything. Commits: nothing; the orchestrator is the sole committer.
## Standard
-Load `it-operations:service-desk` for this department's remit, the artifacts it owns, and when it escalates.
+Load `it-operations:chief-information-officer` for this department's remit, the artifacts it owns, and when it escalates.
Skills in this department follow the conventions in `technology:skill-authoring`: the frontmatter
`name` equals the directory name, and the description carries both what the skill does and when to
reach for it.
diff --git a/.claude/agents/pmo.md b/.claude/agents/pmo.md
index a69d72c..794836e 100644
--- a/.claude/agents/pmo.md
+++ b/.claude/agents/pmo.md
@@ -17,7 +17,7 @@ Reads: anything. Commits: nothing; the orchestrator is the sole committer.
## Standard
-Load `pmo:portfolio-governance` for this department's remit, the artifacts it owns, and when it escalates.
+Load `pmo:head-of-pmo` for this department's remit, the artifacts it owns, and when it escalates.
Skills in this department follow the conventions in `technology:skill-authoring`: the frontmatter
`name` equals the directory name, and the description carries both what the skill does and when to
reach for it.
diff --git a/README.md b/README.md
index b38f45d..18b1900 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
<p align="center">
<a href="https://claude.com/claude-code"><img alt="Built for Claude Code" src="https://img.shields.io/badge/built%20for-Claude%20Code-D97757?style=flat-square"></a>
<img alt="16 departments" src="https://img.shields.io/badge/departments-16-3F4B5B?style=flat-square">
- <img alt="135 skills" src="https://img.shields.io/badge/skills-135-3F4B5B?style=flat-square">
+ <img alt="143 skills" src="https://img.shields.io/badge/skills-143-3F4B5B?style=flat-square">
<a href="LICENSE"><img alt="MIT licensed" src="https://img.shields.io/badge/license-MIT-3F4B5B?style=flat-square"></a>
<a href="CONTRIBUTING.md"><img alt="PRs welcome" src="https://img.shields.io/badge/PRs-welcome-2EA043?style=flat-square"></a>
</p>
@@ -14,7 +14,7 @@
<a href="https://cbrock84.github.io/headcount/org-chart.html">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="docs/assets/org-chart-dark.png">
- <img alt="The headcount org chart — 16 departments, 135 skills, searchable" src="docs/assets/org-chart-light.png" width="840">
+ <img alt="The headcount org chart — 16 departments, 143 skills, searchable" src="docs/assets/org-chart-light.png" width="840">
</picture>
</a>
</p>
@@ -24,7 +24,7 @@
</p>
An agent organization for [Claude Code](https://claude.com/claude-code), structured as a company:
-a chief executive over 16 departments, 135 skills in total.
+a chief executive over 16 departments, 143 skills in total.
Every department is an independently installable plugin, so a project loads only the functions it
needs rather than all of them at once.
@@ -118,11 +118,12 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>IT Operations</b> (CIO) — 7 skills</summary>
+<summary><b>IT Operations</b> (CIO) — 8 skills</summary>
| Skill | What it does |
|---|---|
| `backup-and-recovery` | Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. |
+| `chief-information-officer` | The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. |
| `endpoint-management` | Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. |
| `identity-lifecycle-administration` | Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. |
| `it-asset-management` | Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. |
@@ -150,7 +151,7 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>Marketing</b> (CMO) — 17 skills</summary>
+<summary><b>Marketing</b> (CMO) — 18 skills</summary>
| Skill | What it does |
|---|---|
@@ -160,6 +161,7 @@ to as a subagent with its own exclusive write surface.
| `chief-marketing-officer` | Owns brand, demand generation, content, communications, and how the market understands what the business does. |
| `content-strategy` | Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. |
| `customer-research` | Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. |
+| `events-and-field-marketing` | Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. |
| `marketing-campaign-planner` | Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that g…. |
| `marketing-copywriting` | Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that is not working. |
| `marketing-planning` | Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. |
@@ -210,7 +212,7 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>Finance</b> (CFO) — 9 skills</summary>
+<summary><b>Finance</b> (CFO) — 10 skills</summary>
| Skill | What it does |
|---|---|
@@ -221,20 +223,23 @@ to as a subagent with its own exclusive write surface.
| `financial-reporting-and-close` | Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. |
| `internal-controls-and-audit` | Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. |
| `revenue-recognition` | Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting probl…. |
+| `tax` | Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere…. |
| `treasury-and-liquidity` | Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. |
| `unit-economics` | Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavi…. |
</details>
<details>
-<summary><b>Operations</b> (COO) — 8 skills</summary>
+<summary><b>Operations</b> (COO) — 10 skills</summary>
| Skill | What it does |
|---|---|
| `business-continuity-and-resilience` | Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. |
| `capacity-and-demand-planning` | Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. |
| `chief-operating-officer` | Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. |
+| `facilities-and-workplace` | Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work. |
| `process-design` | Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls tha…. |
+| `procurement-and-sourcing` | Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. |
| `quality-management` | Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. |
| `service-level-management` | Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. |
| `supply-chain-and-logistics` | Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. |
@@ -243,13 +248,14 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>Program Management Office</b> (EPMO / COO) — 6 skills</summary>
+<summary><b>Program Management Office</b> (EPMO / COO) — 7 skills</summary>
| Skill | What it does |
|---|---|
| `benefits-realization` | Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. |
| `change-and-adoption` | Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. |
| `dependency-and-risk-management` | Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. |
+| `head-of-pmo` | The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. |
| `portfolio-governance` | Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. |
| `program-management` | Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. |
| `project-delivery` | Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. |
@@ -297,10 +303,11 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>People</b> (CHRO) — 9 skills</summary>
+<summary><b>People</b> (CHRO) — 10 skills</summary>
| Skill | What it does |
|---|---|
+| `benefits-and-leave` | Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. |
| `chief-human-resources-officer` | Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. |
| `compensation-and-leveling` | Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. |
| `employee-relations` | Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. |
@@ -314,7 +321,7 @@ to as a subagent with its own exclusive write surface.
</details>
<details>
-<summary><b>Legal & Risk</b> (CLO / CCO) — 5 skills · **reviewer-class**</summary>
+<summary><b>Legal & Risk</b> (CLO / CCO) — 6 skills · **reviewer-class**</summary>
| Skill | What it does |
|---|---|
@@ -323,6 +330,7 @@ to as a subagent with its own exclusive write surface.
| `corporate-governance` | Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insura…. |
| `enterprise-risk` | Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing fo…. |
| `privacy-and-data-protection` | Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and br…. |
+| `regulatory-compliance` | Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. |
</details>
diff --git a/docs/DECISION-LOG.md b/docs/DECISION-LOG.md
index 758c972..0251c6e 100644
--- a/docs/DECISION-LOG.md
+++ b/docs/DECISION-LOG.md
@@ -388,9 +388,9 @@ of decisions.
| 4 | Write `docs/AGENT-SURFACES.md`; add first CI workflow running `agent-guard check` | D14 | — | ✅ done |
| 5 | Mark PR #2 ready; squash-merge; delete the branch | D5, D15 | 6+ | ✅ done |
| 6 | Build `security` department + CISO charter, marked reviewer-class | D9, D10, D13 | — | ✅ done |
-| 7 | Deepen `operations`, then `finance`, then `people` | D10 | — | |
+| 7 | Deepen `operations`, then `finance`, then `people` | D10 | — | ✅ done |
| 8 | Catalog the other organizations' public repos — no import | D11 | — | |
-| 9 | Start a separate session for the private sweep | D11 | — | |
+| 9 | ~~Separate session for the private sweep~~ | D11 | — | ✂️ dropped, D30 |
| 10 | Build the vertical generator: core, per-vertical config, one-way emit | D8 | — | |
| 11 | Revisit repo visibility | D16 | after 1 | ✅ done |
@@ -904,3 +904,53 @@ shipping this before the setting is flipped, and it is a single line to revert i
not publish a site.
**To enable:** Settings → Pages → Source: *Deploy from a branch* → Branch: `main`, folder `/docs`.
+
+---
+
+## D30. Coverage QC against public occupational taxonomies — ✅ Resolved
+
+Two questions, settled together: whether the cross-organization repository sweep was worth running,
+and whether the catalog covers what a medium-to-large business actually contains.
+
+**The sweep is dropped.** A manual pass over the those repositories found little beyond
+overlap with GRC roles already covered by `legal-risk` and `security`. Work-queue items 8 and 9 are
+closed rather than deferred — a deferred item nobody intends to do is worse than a closed one,
+because it keeps appearing in every review.
+
+**Coverage was validated against external taxonomies rather than intuition.** Judging one's own
+catalog complete by inspection reliably finds the functions the author already thought of. The
+references used were the **BLS Standard Occupational Classification** major groups 11-0000
+(Management Occupations) and 13-0000 (Business and Financial Operations Occupations) — public,
+cross-industry, and the standard instrument for exactly this question.
+
+**Eight gaps found, all built.** Six were functions the taxonomy names and the catalog did not
+cover:
+
+| Function | SOC codes | Why it was missed |
+|---|---|---|
+| `operations:procurement-and-sourcing` | 11-3061, 13-1023 | Judged covered by `vendor-management`, which is post-contract only. Two separate SOC codes point at the pre-contract discipline; that judgment was wrong. |
+| `finance:tax` | 13-2081, 13-2082 | Zero coverage across nine finance skills. |
+| `people:benefits-and-leave` | 11-3111, 13-1141 | `compensation-and-leveling` covers pay bands, not health, retirement or leave. |
+| `legal-risk:regulatory-compliance` | 13-1041 | Already named as a gap; the taxonomy confirmed it. |
+| `operations:facilities-and-workplace` | 11-3013, 11-9141 | Zero coverage. Also absorbs the administrative-services function from 11-3012, so D12's dissolution of the `administration` department stands. |
+| `marketing:events-and-field-marketing` | 13-1121 | Seventeen marketing skills and no events. |
+
+**Two more were internal inconsistencies the taxonomy did not find and a structural check did.**
+Every department carried a department-head skill except `it-operations` and `pmo` — the two added
+most recently. Their charters had been written to anchor on an arbitrary skill instead, which is a
+workaround I introduced rather than a gap I reported. Fixed with
+`it-operations:chief-information-officer` and `pmo:head-of-pmo`, and both charters now anchor on
+their head like every other.
+
+The CIO skill also states the CTO/CIO boundary explicitly, which D27 split but never wrote down in
+a skill: the CIO runs the technology the company works *on*, the CTO the technology it *sells*.
+
+**What was deliberately not built.** The industry-specific management occupations in SOC 11-9000 —
+education, medical, food service, lodging, gambling, funeral, agricultural and construction — are
+correctly absent from a cross-industry core and belong to the vertical variants in D8. Labor and
+union relations (13-1075) and industrial production management (11-3051) are real but weighted
+toward manufacturing, logistics and retail, so they go to the verticals too.
+
+**Remaining Tier 1**, recorded in the org chart's gaps section: customer experience depth, legal
+depth, corporate strategy depth, and product discovery and prioritization. None is a missing
+function; all are thin coverage of a function already present.
diff --git a/docs/assets/org-chart-dark.png b/docs/assets/org-chart-dark.png
index d5ac19d..c74d6b7 100644
Binary files a/docs/assets/org-chart-dark.png and b/docs/assets/org-chart-dark.png differ
diff --git a/docs/assets/org-chart-light.png b/docs/assets/org-chart-light.png
index 12a76b2..b2b4723 100644
Binary files a/docs/assets/org-chart-light.png and b/docs/assets/org-chart-light.png differ
diff --git a/docs/assets/social-card.html b/docs/assets/social-card.html
index 7b47db5..3c2ef1f 100644
--- a/docs/assets/social-card.html
+++ b/docs/assets/social-card.html
@@ -70,7 +70,7 @@
<div class="rule"></div>
<div class="meta">
<b>16</b> departments <span class="sep">/</span>
- <b>135</b> skills <span class="sep">/</span>
+ <b>143</b> skills <span class="sep">/</span>
MIT <span class="sep">/</span> for Claude Code
</div>
diff --git a/docs/assets/social-preview.png b/docs/assets/social-preview.png
index db7d4d5..168c452 100644
Binary files a/docs/assets/social-preview.png and b/docs/assets/social-preview.png differ
diff --git a/docs/org-chart.html b/docs/org-chart.html
index 06d04f0..d83c876 100644
--- a/docs/org-chart.html
+++ b/docs/org-chart.html
@@ -218,7 +218,7 @@
<div class="figures" id="figures"></div>
<div class="controls">
- <input id="q" type="search" placeholder="Search 135 skills — try “threat”, “pricing”, “backup”…" autocomplete="off">
+ <input id="q" type="search" placeholder="Search 143 skills — try “threat”, “pricing”, “backup”…" autocomplete="off">
<button class="btn" id="revonly" aria-pressed="false">Reviewer-class only</button>
<button class="btn" id="expand">Expand all</button>
<span id="count"></span>
@@ -248,7 +248,7 @@
</div>
<script>
-const DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "reviewer": false, "skills": [{"name": "agent-hierarchy", "summary": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independ…", "trigger": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/agent-hierarchy/SKILL.md"}, {"name": "ai-research-analyst", "summary": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with th…", "trigger": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ai-research-analyst/SKILL.md"}, {"name": "business-growth-consultant", "summary": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everyth…", "trigger": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/business-growth-consultant/SKILL.md"}, {"name": "ceo-advisor", "summary": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have t…", "trigger": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ceo-advisor/SKILL.md"}, {"name": "chief-executive", "summary": "Sets direction, allocates capital and attention, and makes the calls no one else can make", "trigger": "Sets direction, allocates capital and attention, and makes the calls no one else can make. Use this when a decision spans more than one function, when priorities conflict and something must be cut, when a plan needs pressure-testing before commitment, or when the question is what the organization should do rather than how to do it. Also use to route a request to the right executive when it is unclear who owns it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/chief-executive/SKILL.md"}, {"name": "saas-idea-validator", "summary": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather t…", "trigger": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when deciding whether something is worth pursuing, when assessing competition or willingness to pay, or when a validated idea needs a first-customers and MVP plan. Default to scrutiny; the useful answer is usually the unwelcome one.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/saas-idea-validator/SKILL.md"}]}, {"slug": "technology", "title": "Technology", "exec": "CTO / CIO", "reviewer": false, "skills": [{"name": "ai-workflow-architect", "summary": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system,…", "trigger": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/ai-workflow-architect/SKILL.md"}, {"name": "api-design", "summary": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility", "trigger": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/api-design/SKILL.md"}, {"name": "branch-and-worktree-workflow", "summary": "Isolates feature work in its own branch or worktree and integrates it cleanly when done", "trigger": "Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/branch-and-worktree-workflow/SKILL.md"}, {"name": "chief-technology-officer", "summary": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems", "trigger": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/chief-technology-officer/SKILL.md"}, {"name": "cloud-infrastructure", "summary": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost", "trigger": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/cloud-infrastructure/SKILL.md"}, {"name": "code-review", "summary": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work", "trigger": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/code-review/SKILL.md"}, {"name": "completion-verification", "summary": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was…", "trigger": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/completion-verification/SKILL.md"}, {"name": "implementation-planning", "summary": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints", "trigger": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/implementation-planning/SKILL.md"}, {"name": "observability-and-reliability", "summary": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure", "trigger": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/observability-and-reliability/SKILL.md"}, {"name": "parallel-agent-delivery", "summary": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly", "trigger": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/parallel-agent-delivery/SKILL.md"}, {"name": "prompt-optimizer", "summary": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it acros…", "trigger": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/prompt-optimizer/SKILL.md"}, {"name": "release-and-deployment", "summary": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes", "trigger": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/release-and-deployment/SKILL.md"}, {"name": "skill-authoring", "summary": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do", "trigger": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/skill-authoring/SKILL.md"}, {"name": "solution-architecture", "summary": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why", "trigger": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-architecture/SKILL.md"}, {"name": "solution-exploration", "summary": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options wit…", "trigger": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-exploration/SKILL.md"}, {"name": "systematic-debugging", "summary": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix", "trigger": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/systematic-debugging/SKILL.md"}, {"name": "technical-debt-management", "summary": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms", "trigger": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/technical-debt-management/SKILL.md"}, {"name": "test-driven-development", "summary": "Drives implementation by writing a failing test first, then the smallest code that passes it", "trigger": "Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/test-driven-development/SKILL.md"}]}, {"slug": "security", "title": "Security", "exec": "CISO", "reviewer": true, "skills": [{"name": "access-and-identity", "summary": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process", "trigger": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/access-and-identity/SKILL.md"}, {"name": "chief-information-security-officer", "summary": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work tha…", "trigger": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure. Use this for a security strategy or program decision, when a technical choice creates security risk that needs a verdict, when deciding whether to accept or block a risk, when standing up a security function, or when security and delivery priorities conflict and someone has to decide.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/chief-information-security-officer/SKILL.md"}, {"name": "incident-response", "summary": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward", "trigger": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/incident-response/SKILL.md"}, {"name": "security-architecture-review", "summary": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-deve…", "trigger": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/security-architecture-review/SKILL.md"}, {"name": "threat-modeling", "summary": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and th…", "trigger": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/threat-modeling/SKILL.md"}, {"name": "vulnerability-management", "summary": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking,…", "trigger": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/vulnerability-management/SKILL.md"}]}, {"slug": "it-operations", "title": "IT Operations", "exec": "CIO", "reviewer": false, "skills": [{"name": "backup-and-recovery", "summary": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work", "trigger": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/backup-and-recovery/SKILL.md"}, {"name": "endpoint-management", "summary": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices", "trigger": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/endpoint-management/SKILL.md"}, {"name": "identity-lifecycle-administration", "summary": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning", "trigger": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. Use this to set up or fix joiner-mover-leaver, deprovision someone completely, clean up accumulated access, audit group membership, or find accounts that outlived their owners.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/identity-lifecycle-administration/SKILL.md"}, {"name": "it-asset-management", "summary": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal", "trigger": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/it-asset-management/SKILL.md"}, {"name": "network-administration", "summary": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems", "trigger": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/network-administration/SKILL.md"}, {"name": "service-desk", "summary": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it", "trigger": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/service-desk/SKILL.md"}, {"name": "systems-administration", "summary": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents", "trigger": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/systems-administration/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "reviewer": false, "skills": [{"name": "brand-identity", "summary": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across prod…", "trigger": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide how a brand should express itself in an unfamiliar format.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/brand-identity/SKILL.md"}, {"name": "chief-product-officer", "summary": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release", "trigger": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market disagree about what a release is for. Also use for roadmap sequencing and for killing work that is not earning its place.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/chief-product-officer/SKILL.md"}, {"name": "design-styles", "summary": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own t…", "trigger": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions, when an interface reads as generic, or when restyling something without changing its structure.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-styles/SKILL.md"}, {"name": "design-system", "summary": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rule…", "trigger": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-system/SKILL.md"}, {"name": "interface-craft", "summary": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered pro…", "trigger": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-craft/SKILL.md"}, {"name": "interface-redesign", "summary": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished,…", "trigger": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or rebuild, or when a screen needs to look substantially better with limited effort.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-redesign/SKILL.md"}, {"name": "presentation-design", "summary": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one", "trigger": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one. Use this to build or fix a pitch deck, board deck, or conference talk; to design a banner, social graphic, or one-pager; or when a deck is dense, unfocused, or being read aloud from the slides.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/presentation-design/SKILL.md"}, {"name": "ux-product-auditor", "summary": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a se…", "trigger": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use `interface-craft`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/ux-product-auditor/SKILL.md"}, {"name": "visual-reference-generation", "summary": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief co…", "trigger": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/visual-reference-generation/SKILL.md"}]}, {"slug": "marketing", "title": "Marketing", "exec": "CMO", "reviewer": false, "skills": [{"name": "behavioral-marketing", "summary": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how frami…", "trigger": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how framing, defaults, sequencing, and social context change behavior. Use this to diagnose why a well-argued offer is not converting, to structure choices and pricing presentation, to design an experience around how attention and memory work, or to pressure-test whether a persuasion tactic is legitimate or manipulative.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/behavioral-marketing/SKILL.md"}, {"name": "brand-voice", "summary": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from", "trigger": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from. Use this before drafting any content for a new brand or client, when output keeps coming back sounding generic, when several writers need to sound like one, or when a voice needs defining without existing samples to learn from.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/brand-voice/SKILL.md"}, {"name": "chief-content-officer", "summary": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what…", "trigger": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-content-officer/SKILL.md"}, {"name": "chief-marketing-officer", "summary": "Owns brand, demand generation, content, communications, and how the market understands what the business does", "trigger": "Owns brand, demand generation, content, communications, and how the market understands what the business does. Use this to set marketing strategy, allocate budget across channels, decide positioning and messaging, judge whether a campaign is worth running, diagnose why demand has stalled, or arbitrate between brand-building and short-term acquisition. Also use to decide which marketing work to stop.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-marketing-officer/SKILL.md"}, {"name": "content-strategy", "summary": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic", "trigger": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/content-strategy/SKILL.md"}, {"name": "customer-research", "summary": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions", "trigger": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/customer-research/SKILL.md"}, {"name": "marketing-campaign-planner", "summary": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the c…", "trigger": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that gets it out the door. Use this to plan a launch or campaign, sequence a go-to-market push, pressure-test a campaign before committing budget, or turn a product change into a coordinated set of activity. For ongoing channel programs rather than a bounded push, use `marketing-planning`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-campaign-planner/SKILL.md"}, {"name": "marketing-copywriting", "summary": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that…", "trigger": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that is not working. Use this to write or rewrite page copy, tighten a draft, fix copy that is vague or feature-led, adapt one message across formats, or review copy before it ships.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-copywriting/SKILL.md"}, {"name": "marketing-planning", "summary": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked", "trigger": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-planning/SKILL.md"}, {"name": "newsletter-writer", "summary": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where ther…", "trigger": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/newsletter-writer/SKILL.md"}, {"name": "partnership-marketing", "summary": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrange…", "trigger": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrangements. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/partnership-marketing/SKILL.md"}, {"name": "positioning-and-messaging", "summary": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits", "trigger": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits. Use this when messaging is inconsistent across channels, when prospects misunderstand what the product does, when entering a new segment, when competitors are being compared against you unfavorably, or before any campaign, launch, or site rewrite.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/positioning-and-messaging/SKILL.md"}, {"name": "public-relations", "summary": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response", "trigger": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/public-relations/SKILL.md"}, {"name": "social-post-craft", "summary": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publish…", "trigger": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publishing. Use this to draft a post, rewrite one that underperformed, turn a longer piece into social content, sharpen an opening, or judge whether a draft is worth publishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/social-post-craft/SKILL.md"}, {"name": "video-content", "summary": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watc…", "trigger": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/video-content/SKILL.md"}, {"name": "visual-content", "summary": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the gene…", "trigger": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/visual-content/SKILL.md"}, {"name": "youtube-producer", "summary": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosi…", "trigger": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/youtube-producer/SKILL.md"}]}, {"slug": "demand-generation", "title": "Demand Generation", "exec": "CMO", "reviewer": false, "skills": [{"name": "ai-search-optimization", "summary": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your…", "trigger": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/ai-search-optimization/SKILL.md"}, {"name": "app-store-optimization", "summary": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns…", "trigger": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/app-store-optimization/SKILL.md"}, {"name": "experimentation", "summary": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation", "trigger": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation. Use this to plan a test, judge whether a result is real, build an experimentation program, decide what to test next, or diagnose why tests keep producing inconclusive or non-replicating results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/experimentation/SKILL.md"}, {"name": "landing-page-cro-expert", "summary": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines,…", "trigger": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines, hero copy and calls to action, and prioritizing which changes to test first. Use this when a page underperforms, when someone pastes a URL or screenshot asking what is wrong, when writing a new page, or when deciding which conversion changes are worth testing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md"}, {"name": "lead-capture", "summary": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them", "trigger": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them. Use this to design or improve a lead magnet, plan a free tool, add or fix popups and overlays, improve form conversion, or decide what is worth gating and what should stay open.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lead-capture/SKILL.md"}, {"name": "lifecycle-messaging", "summary": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segm…", "trigger": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lifecycle-messaging/SKILL.md"}, {"name": "listing-distribution", "summary": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators", "trigger": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/listing-distribution/SKILL.md"}, {"name": "marketing-analytics", "summary": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them", "trigger": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them. Use this to instrument a site or product, audit tracking nobody trusts, choose or interpret an attribution model, build reporting that answers a specific question, or reconcile numbers that disagree between tools.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/marketing-analytics/SKILL.md"}, {"name": "paid-advertising", "summary": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the ana…", "trigger": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide budget allocation, or judge whether a channel is working.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/paid-advertising/SKILL.md"}, {"name": "programmatic-seo", "summary": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture lon…", "trigger": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture long-tail demand at scale. Use this when there is a repeating query pattern with real volume, when a dataset could answer many similar searches, or to judge whether a programmatic approach is viable before building it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/programmatic-seo/SKILL.md"}, {"name": "seo-strategy", "summary": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions th…", "trigger": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/seo-strategy/SKILL.md"}]}, {"slug": "revenue", "title": "Revenue", "exec": "CRO", "reviewer": false, "skills": [{"name": "activation", "summary": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone bec…", "trigger": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/activation/SKILL.md"}, {"name": "chief-revenue-officer", "summary": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships", "trigger": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/chief-revenue-officer/SKILL.md"}, {"name": "outbound-prospecting", "summary": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and th…", "trigger": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/outbound-prospecting/SKILL.md"}, {"name": "pricing-and-packaging", "summary": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction", "trigger": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/pricing-and-packaging/SKILL.md"}, {"name": "referral-programs", "summary": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control", "trigger": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/referral-programs/SKILL.md"}, {"name": "retention", "summary": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underne…", "trigger": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/retention/SKILL.md"}, {"name": "revenue-operations", "summary": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketi…", "trigger": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff. Use this to fix a broken handoff, define lifecycle stages, improve forecast accuracy, clean up CRM data, design territory or routing rules, or diagnose why pipeline numbers are not trusted.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/revenue-operations/SKILL.md"}, {"name": "sales-enablement", "summary": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies", "trigger": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/sales-enablement/SKILL.md"}]}, {"slug": "finance", "title": "Finance", "exec": "CFO", "reviewer": false, "skills": [{"name": "budgeting-and-forecasting", "summary": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals aga…", "trigger": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/budgeting-and-forecasting/SKILL.md"}, {"name": "capital-allocation", "summary": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike", "trigger": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-allocation/SKILL.md"}, {"name": "chief-financial-officer", "summary": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on", "trigger": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/chief-financial-officer/SKILL.md"}, {"name": "financial-modeling", "summary": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and…", "trigger": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-modeling/SKILL.md"}, {"name": "financial-reporting-and-close", "summary": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read", "trigger": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. Use this to shorten or stabilise a monthly close, design a close checklist, investigate a variance, structure management reporting, or work out why the numbers keep changing after close.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-reporting-and-close/SKILL.md"}, {"name": "internal-controls-and-audit", "summary": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit", "trigger": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is genuinely broken.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/internal-controls-and-audit/SKILL.md"}, {"name": "revenue-recognition", "summary": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create a…", "trigger": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/revenue-recognition/SKILL.md"}, {"name": "treasury-and-liquidity", "summary": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure", "trigger": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/treasury-and-liquidity/SKILL.md"}, {"name": "unit-economics", "summary": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and th…", "trigger": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/unit-economics/SKILL.md"}]}, {"slug": "operations", "title": "Operations", "exec": "COO", "reviewer": false, "skills": [{"name": "business-continuity-and-resilience", "summary": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work", "trigger": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/business-continuity-and-resilience/SKILL.md"}, {"name": "capacity-and-demand-planning", "summary": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity", "trigger": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/capacity-and-demand-planning/SKILL.md"}, {"name": "chief-operating-officer", "summary": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and serv…", "trigger": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/chief-operating-officer/SKILL.md"}, {"name": "process-design", "summary": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and buildi…", "trigger": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/process-design/SKILL.md"}, {"name": "quality-management", "summary": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement", "trigger": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/quality-management/SKILL.md"}, {"name": "service-level-management", "summary": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches", "trigger": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/service-level-management/SKILL.md"}, {"name": "supply-chain-and-logistics", "summary": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk", "trigger": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/supply-chain-and-logistics/SKILL.md"}, {"name": "vendor-management", "summary": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit", "trigger": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/vendor-management/SKILL.md"}]}, {"slug": "pmo", "title": "Program Management Office", "exec": "EPMO / COO", "reviewer": false, "skills": [{"name": "benefits-realization", "summary": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-impleme…", "trigger": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/benefits-realization/SKILL.md"}, {"name": "change-and-adoption", "summary": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption", "trigger": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/change-and-adoption/SKILL.md"}, {"name": "dependency-and-risk-management", "summary": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work", "trigger": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materialising unmanaged.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/dependency-and-risk-management/SKILL.md"}, {"name": "portfolio-governance", "summary": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things", "trigger": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/portfolio-governance/SKILL.md"}, {"name": "program-management", "summary": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving", "trigger": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/program-management/SKILL.md"}, {"name": "project-delivery", "summary": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips", "trigger": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/project-delivery/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "reviewer": false, "skills": [{"name": "chief-customer-officer", "summary": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product", "trigger": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/chief-customer-officer/SKILL.md"}, {"name": "escalation-management", "summary": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a r…", "trigger": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/escalation-management/SKILL.md"}, {"name": "self-service-and-knowledge", "summary": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability,…", "trigger": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md"}, {"name": "support-operations", "summary": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working", "trigger": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor quality, or decide what to automate.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/support-operations/SKILL.md"}, {"name": "voice-of-customer", "summary": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closi…", "trigger": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/voice-of-customer/SKILL.md"}]}, {"slug": "data-analytics", "title": "Data & Analytics", "exec": "CDO", "reviewer": false, "skills": [{"name": "ai-ml-governance", "summary": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or ret…", "trigger": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/ai-ml-governance/SKILL.md"}, {"name": "business-intelligence", "summary": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dash…", "trigger": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/business-intelligence/SKILL.md"}, {"name": "chief-data-officer", "summary": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top", "trigger": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/chief-data-officer/SKILL.md"}, {"name": "data-engineering", "summary": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery", "trigger": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-engineering/SKILL.md"}, {"name": "data-governance", "summary": "Establishes ownership, definitions, quality, access, and lineage for the organization's data", "trigger": "Establishes ownership, definitions, quality, access, and lineage for the organization's data. Use this when metrics disagree between teams, when nobody knows which dataset is authoritative, when setting up data ownership or access policy, when data quality is unreliable, or before opening a dataset to a wider audience.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-governance/SKILL.md"}, {"name": "data-modeling", "summary": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer an…", "trigger": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or diagnose why queries are slow, wrong, or impossible to write.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-modeling/SKILL.md"}]}, {"slug": "corporate-strategy", "title": "Corporate Strategy", "exec": "CSO", "reviewer": false, "skills": [{"name": "chief-strategy-officer", "summary": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and plann…", "trigger": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md"}, {"name": "mergers-and-acquisitions", "summary": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning", "trigger": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md"}, {"name": "portfolio-strategy", "summary": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence", "trigger": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide market entry or exit, structure a portfolio review, or when several initiatives compete for the same limited investment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md"}, {"name": "scenario-planning", "summary": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-te…", "trigger": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/scenario-planning/SKILL.md"}, {"name": "strategic-alliances", "summary": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM re…", "trigger": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/strategic-alliances/SKILL.md"}]}, {"slug": "people", "title": "People", "exec": "CHRO", "reviewer": false, "skills": [{"name": "chief-human-resources-officer", "summary": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations", "trigger": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/chief-human-resources-officer/SKILL.md"}, {"name": "compensation-and-leveling", "summary": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promoti…", "trigger": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/compensation-and-leveling/SKILL.md"}, {"name": "employee-relations", "summary": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly", "trigger": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employee-relations/SKILL.md"}, {"name": "hiring-and-interviewing", "summary": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself", "trigger": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/hiring-and-interviewing/SKILL.md"}, {"name": "learning-and-development", "summary": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility", "trigger": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/learning-and-development/SKILL.md"}, {"name": "onboarding-and-offboarding", "summary": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits", "trigger": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner or leaver.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/onboarding-and-offboarding/SKILL.md"}, {"name": "org-design", "summary": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the s…", "trigger": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/org-design/SKILL.md"}, {"name": "performance-management", "summary": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance", "trigger": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/performance-management/SKILL.md"}, {"name": "workforce-planning", "summary": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget", "trigger": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/workforce-planning/SKILL.md"}]}, {"slug": "legal-risk", "title": "Legal & Risk", "exec": "CLO / CCO", "reviewer": true, "skills": [{"name": "chief-legal-and-risk-officer", "summary": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness", "trigger": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit or certification, or when a plan may create obligations the business cannot meet. Also use to decide whether a risk should be accepted, mitigated, or refused.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/chief-legal-and-risk-officer/SKILL.md"}, {"name": "contract-review", "summary": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, prop…", "trigger": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback positions and approval thresholds, or assess exposure in terms already agreed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/contract-review/SKILL.md"}, {"name": "corporate-governance", "summary": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of au…", "trigger": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval authority, review insurance and continuity coverage, establish a retention policy, or work out where a responsibility belongs when it falls between functions.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/corporate-governance/SKILL.md"}, {"name": "enterprise-risk", "summary": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, a…", "trigger": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/enterprise-risk/SKILL.md"}, {"name": "privacy-and-data-protection", "summary": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject…", "trigger": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request arrives, when assessing exposure under GDPR or US state privacy laws, or when preparing for a privacy review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/privacy-and-data-protection/SKILL.md"}]}];
+const DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "reviewer": false, "skills": [{"name": "agent-hierarchy", "summary": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independ…", "trigger": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/agent-hierarchy/SKILL.md"}, {"name": "ai-research-analyst", "summary": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with th…", "trigger": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ai-research-analyst/SKILL.md"}, {"name": "business-growth-consultant", "summary": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everyth…", "trigger": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/business-growth-consultant/SKILL.md"}, {"name": "ceo-advisor", "summary": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have t…", "trigger": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ceo-advisor/SKILL.md"}, {"name": "chief-executive", "summary": "Sets direction, allocates capital and attention, and makes the calls no one else can make", "trigger": "Sets direction, allocates capital and attention, and makes the calls no one else can make. Use this when a decision spans more than one function, when priorities conflict and something must be cut, when a plan needs pressure-testing before commitment, or when the question is what the organization should do rather than how to do it. Also use to route a request to the right executive when it is unclear who owns it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/chief-executive/SKILL.md"}, {"name": "saas-idea-validator", "summary": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather t…", "trigger": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when deciding whether something is worth pursuing, when assessing competition or willingness to pay, or when a validated idea needs a first-customers and MVP plan. Default to scrutiny; the useful answer is usually the unwelcome one.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/saas-idea-validator/SKILL.md"}]}, {"slug": "technology", "title": "Technology", "exec": "CTO / CIO", "reviewer": false, "skills": [{"name": "ai-workflow-architect", "summary": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system,…", "trigger": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/ai-workflow-architect/SKILL.md"}, {"name": "api-design", "summary": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility", "trigger": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/api-design/SKILL.md"}, {"name": "branch-and-worktree-workflow", "summary": "Isolates feature work in its own branch or worktree and integrates it cleanly when done", "trigger": "Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/branch-and-worktree-workflow/SKILL.md"}, {"name": "chief-technology-officer", "summary": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems", "trigger": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/chief-technology-officer/SKILL.md"}, {"name": "cloud-infrastructure", "summary": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost", "trigger": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/cloud-infrastructure/SKILL.md"}, {"name": "code-review", "summary": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work", "trigger": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/code-review/SKILL.md"}, {"name": "completion-verification", "summary": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was…", "trigger": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/completion-verification/SKILL.md"}, {"name": "implementation-planning", "summary": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints", "trigger": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/implementation-planning/SKILL.md"}, {"name": "observability-and-reliability", "summary": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure", "trigger": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/observability-and-reliability/SKILL.md"}, {"name": "parallel-agent-delivery", "summary": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly", "trigger": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/parallel-agent-delivery/SKILL.md"}, {"name": "prompt-optimizer", "summary": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it acros…", "trigger": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/prompt-optimizer/SKILL.md"}, {"name": "release-and-deployment", "summary": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes", "trigger": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/release-and-deployment/SKILL.md"}, {"name": "skill-authoring", "summary": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do", "trigger": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/skill-authoring/SKILL.md"}, {"name": "solution-architecture", "summary": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why", "trigger": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-architecture/SKILL.md"}, {"name": "solution-exploration", "summary": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options wit…", "trigger": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-exploration/SKILL.md"}, {"name": "systematic-debugging", "summary": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix", "trigger": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/systematic-debugging/SKILL.md"}, {"name": "technical-debt-management", "summary": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms", "trigger": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/technical-debt-management/SKILL.md"}, {"name": "test-driven-development", "summary": "Drives implementation by writing a failing test first, then the smallest code that passes it", "trigger": "Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/test-driven-development/SKILL.md"}]}, {"slug": "security", "title": "Security", "exec": "CISO", "reviewer": true, "skills": [{"name": "access-and-identity", "summary": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process", "trigger": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/access-and-identity/SKILL.md"}, {"name": "chief-information-security-officer", "summary": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work tha…", "trigger": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure. Use this for a security strategy or program decision, when a technical choice creates security risk that needs a verdict, when deciding whether to accept or block a risk, when standing up a security function, or when security and delivery priorities conflict and someone has to decide.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/chief-information-security-officer/SKILL.md"}, {"name": "incident-response", "summary": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward", "trigger": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/incident-response/SKILL.md"}, {"name": "security-architecture-review", "summary": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-deve…", "trigger": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/security-architecture-review/SKILL.md"}, {"name": "threat-modeling", "summary": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and th…", "trigger": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/threat-modeling/SKILL.md"}, {"name": "vulnerability-management", "summary": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking,…", "trigger": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/vulnerability-management/SKILL.md"}]}, {"slug": "it-operations", "title": "IT Operations", "exec": "CIO", "reviewer": false, "skills": [{"name": "backup-and-recovery", "summary": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work", "trigger": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/backup-and-recovery/SKILL.md"}, {"name": "chief-information-officer", "summary": "The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering", "trigger": "The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/chief-information-officer/SKILL.md"}, {"name": "endpoint-management", "summary": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices", "trigger": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/endpoint-management/SKILL.md"}, {"name": "identity-lifecycle-administration", "summary": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning", "trigger": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. Use this to set up or fix joiner-mover-leaver, deprovision someone completely, clean up accumulated access, audit group membership, or find accounts that outlived their owners.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/identity-lifecycle-administration/SKILL.md"}, {"name": "it-asset-management", "summary": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal", "trigger": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/it-asset-management/SKILL.md"}, {"name": "network-administration", "summary": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems", "trigger": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/network-administration/SKILL.md"}, {"name": "service-desk", "summary": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it", "trigger": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/service-desk/SKILL.md"}, {"name": "systems-administration", "summary": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents", "trigger": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/systems-administration/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "reviewer": false, "skills": [{"name": "brand-identity", "summary": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across prod…", "trigger": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide how a brand should express itself in an unfamiliar format.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/brand-identity/SKILL.md"}, {"name": "chief-product-officer", "summary": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release", "trigger": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market disagree about what a release is for. Also use for roadmap sequencing and for killing work that is not earning its place.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/chief-product-officer/SKILL.md"}, {"name": "design-styles", "summary": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own t…", "trigger": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions, when an interface reads as generic, or when restyling something without changing its structure.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-styles/SKILL.md"}, {"name": "design-system", "summary": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rule…", "trigger": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-system/SKILL.md"}, {"name": "interface-craft", "summary": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered pro…", "trigger": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-craft/SKILL.md"}, {"name": "interface-redesign", "summary": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished,…", "trigger": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or rebuild, or when a screen needs to look substantially better with limited effort.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-redesign/SKILL.md"}, {"name": "presentation-design", "summary": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one", "trigger": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one. Use this to build or fix a pitch deck, board deck, or conference talk; to design a banner, social graphic, or one-pager; or when a deck is dense, unfocused, or being read aloud from the slides.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/presentation-design/SKILL.md"}, {"name": "ux-product-auditor", "summary": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a se…", "trigger": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use `interface-craft`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/ux-product-auditor/SKILL.md"}, {"name": "visual-reference-generation", "summary": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief co…", "trigger": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/visual-reference-generation/SKILL.md"}]}, {"slug": "marketing", "title": "Marketing", "exec": "CMO", "reviewer": false, "skills": [{"name": "behavioral-marketing", "summary": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how frami…", "trigger": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how framing, defaults, sequencing, and social context change behavior. Use this to diagnose why a well-argued offer is not converting, to structure choices and pricing presentation, to design an experience around how attention and memory work, or to pressure-test whether a persuasion tactic is legitimate or manipulative.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/behavioral-marketing/SKILL.md"}, {"name": "brand-voice", "summary": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from", "trigger": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from. Use this before drafting any content for a new brand or client, when output keeps coming back sounding generic, when several writers need to sound like one, or when a voice needs defining without existing samples to learn from.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/brand-voice/SKILL.md"}, {"name": "chief-content-officer", "summary": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what…", "trigger": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-content-officer/SKILL.md"}, {"name": "chief-marketing-officer", "summary": "Owns brand, demand generation, content, communications, and how the market understands what the business does", "trigger": "Owns brand, demand generation, content, communications, and how the market understands what the business does. Use this to set marketing strategy, allocate budget across channels, decide positioning and messaging, judge whether a campaign is worth running, diagnose why demand has stalled, or arbitrate between brand-building and short-term acquisition. Also use to decide which marketing work to stop.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-marketing-officer/SKILL.md"}, {"name": "content-strategy", "summary": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic", "trigger": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/content-strategy/SKILL.md"}, {"name": "customer-research", "summary": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions", "trigger": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/customer-research/SKILL.md"}, {"name": "events-and-field-marketing", "summary": "Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked", "trigger": "Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/events-and-field-marketing/SKILL.md"}, {"name": "marketing-campaign-planner", "summary": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the c…", "trigger": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that gets it out the door. Use this to plan a launch or campaign, sequence a go-to-market push, pressure-test a campaign before committing budget, or turn a product change into a coordinated set of activity. For ongoing channel programs rather than a bounded push, use `marketing-planning`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-campaign-planner/SKILL.md"}, {"name": "marketing-copywriting", "summary": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that…", "trigger": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that is not working. Use this to write or rewrite page copy, tighten a draft, fix copy that is vague or feature-led, adapt one message across formats, or review copy before it ships.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-copywriting/SKILL.md"}, {"name": "marketing-planning", "summary": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked", "trigger": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-planning/SKILL.md"}, {"name": "newsletter-writer", "summary": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where ther…", "trigger": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/newsletter-writer/SKILL.md"}, {"name": "partnership-marketing", "summary": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrange…", "trigger": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrangements. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/partnership-marketing/SKILL.md"}, {"name": "positioning-and-messaging", "summary": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits", "trigger": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits. Use this when messaging is inconsistent across channels, when prospects misunderstand what the product does, when entering a new segment, when competitors are being compared against you unfavorably, or before any campaign, launch, or site rewrite.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/positioning-and-messaging/SKILL.md"}, {"name": "public-relations", "summary": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response", "trigger": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/public-relations/SKILL.md"}, {"name": "social-post-craft", "summary": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publish…", "trigger": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publishing. Use this to draft a post, rewrite one that underperformed, turn a longer piece into social content, sharpen an opening, or judge whether a draft is worth publishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/social-post-craft/SKILL.md"}, {"name": "video-content", "summary": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watc…", "trigger": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/video-content/SKILL.md"}, {"name": "visual-content", "summary": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the gene…", "trigger": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/visual-content/SKILL.md"}, {"name": "youtube-producer", "summary": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosi…", "trigger": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/youtube-producer/SKILL.md"}]}, {"slug": "demand-generation", "title": "Demand Generation", "exec": "CMO", "reviewer": false, "skills": [{"name": "ai-search-optimization", "summary": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your…", "trigger": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/ai-search-optimization/SKILL.md"}, {"name": "app-store-optimization", "summary": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns…", "trigger": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/app-store-optimization/SKILL.md"}, {"name": "experimentation", "summary": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation", "trigger": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation. Use this to plan a test, judge whether a result is real, build an experimentation program, decide what to test next, or diagnose why tests keep producing inconclusive or non-replicating results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/experimentation/SKILL.md"}, {"name": "landing-page-cro-expert", "summary": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines,…", "trigger": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines, hero copy and calls to action, and prioritizing which changes to test first. Use this when a page underperforms, when someone pastes a URL or screenshot asking what is wrong, when writing a new page, or when deciding which conversion changes are worth testing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md"}, {"name": "lead-capture", "summary": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them", "trigger": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them. Use this to design or improve a lead magnet, plan a free tool, add or fix popups and overlays, improve form conversion, or decide what is worth gating and what should stay open.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lead-capture/SKILL.md"}, {"name": "lifecycle-messaging", "summary": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segm…", "trigger": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lifecycle-messaging/SKILL.md"}, {"name": "listing-distribution", "summary": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators", "trigger": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/listing-distribution/SKILL.md"}, {"name": "marketing-analytics", "summary": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them", "trigger": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them. Use this to instrument a site or product, audit tracking nobody trusts, choose or interpret an attribution model, build reporting that answers a specific question, or reconcile numbers that disagree between tools.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/marketing-analytics/SKILL.md"}, {"name": "paid-advertising", "summary": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the ana…", "trigger": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide budget allocation, or judge whether a channel is working.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/paid-advertising/SKILL.md"}, {"name": "programmatic-seo", "summary": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture lon…", "trigger": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture long-tail demand at scale. Use this when there is a repeating query pattern with real volume, when a dataset could answer many similar searches, or to judge whether a programmatic approach is viable before building it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/programmatic-seo/SKILL.md"}, {"name": "seo-strategy", "summary": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions th…", "trigger": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/seo-strategy/SKILL.md"}]}, {"slug": "revenue", "title": "Revenue", "exec": "CRO", "reviewer": false, "skills": [{"name": "activation", "summary": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone bec…", "trigger": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/activation/SKILL.md"}, {"name": "chief-revenue-officer", "summary": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships", "trigger": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/chief-revenue-officer/SKILL.md"}, {"name": "outbound-prospecting", "summary": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and th…", "trigger": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/outbound-prospecting/SKILL.md"}, {"name": "pricing-and-packaging", "summary": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction", "trigger": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/pricing-and-packaging/SKILL.md"}, {"name": "referral-programs", "summary": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control", "trigger": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/referral-programs/SKILL.md"}, {"name": "retention", "summary": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underne…", "trigger": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/retention/SKILL.md"}, {"name": "revenue-operations", "summary": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketi…", "trigger": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff. Use this to fix a broken handoff, define lifecycle stages, improve forecast accuracy, clean up CRM data, design territory or routing rules, or diagnose why pipeline numbers are not trusted.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/revenue-operations/SKILL.md"}, {"name": "sales-enablement", "summary": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies", "trigger": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/sales-enablement/SKILL.md"}]}, {"slug": "finance", "title": "Finance", "exec": "CFO", "reviewer": false, "skills": [{"name": "budgeting-and-forecasting", "summary": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals aga…", "trigger": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/budgeting-and-forecasting/SKILL.md"}, {"name": "capital-allocation", "summary": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike", "trigger": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-allocation/SKILL.md"}, {"name": "chief-financial-officer", "summary": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on", "trigger": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/chief-financial-officer/SKILL.md"}, {"name": "financial-modeling", "summary": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and…", "trigger": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-modeling/SKILL.md"}, {"name": "financial-reporting-and-close", "summary": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read", "trigger": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. Use this to shorten or stabilise a monthly close, design a close checklist, investigate a variance, structure management reporting, or work out why the numbers keep changing after close.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-reporting-and-close/SKILL.md"}, {"name": "internal-controls-and-audit", "summary": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit", "trigger": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is genuinely broken.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/internal-controls-and-audit/SKILL.md"}, {"name": "revenue-recognition", "summary": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create a…", "trigger": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/revenue-recognition/SKILL.md"}, {"name": "tax", "summary": "Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or sel…", "trigger": "Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/tax/SKILL.md"}, {"name": "treasury-and-liquidity", "summary": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure", "trigger": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/treasury-and-liquidity/SKILL.md"}, {"name": "unit-economics", "summary": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and th…", "trigger": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/unit-economics/SKILL.md"}]}, {"slug": "operations", "title": "Operations", "exec": "COO", "reviewer": false, "skills": [{"name": "business-continuity-and-resilience", "summary": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work", "trigger": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/business-continuity-and-resilience/SKILL.md"}, {"name": "capacity-and-demand-planning", "summary": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity", "trigger": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/capacity-and-demand-planning/SKILL.md"}, {"name": "chief-operating-officer", "summary": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and serv…", "trigger": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/chief-operating-officer/SKILL.md"}, {"name": "facilities-and-workplace", "summary": "Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work", "trigger": "Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work. Use this to plan space, evaluate a lease or office move, set up a hybrid workplace, handle facilities incidents, or decide what office services are worth funding.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/facilities-and-workplace/SKILL.md"}, {"name": "process-design", "summary": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and buildi…", "trigger": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/process-design/SKILL.md"}, {"name": "procurement-and-sourcing", "summary": "Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists", "trigger": "Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring uncontrolled spending under management.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/procurement-and-sourcing/SKILL.md"}, {"name": "quality-management", "summary": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement", "trigger": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/quality-management/SKILL.md"}, {"name": "service-level-management", "summary": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches", "trigger": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/service-level-management/SKILL.md"}, {"name": "supply-chain-and-logistics", "summary": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk", "trigger": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/supply-chain-and-logistics/SKILL.md"}, {"name": "vendor-management", "summary": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit", "trigger": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/vendor-management/SKILL.md"}]}, {"slug": "pmo", "title": "Program Management Office", "exec": "EPMO / COO", "reviewer": false, "skills": [{"name": "benefits-realization", "summary": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-impleme…", "trigger": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/benefits-realization/SKILL.md"}, {"name": "change-and-adoption", "summary": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption", "trigger": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/change-and-adoption/SKILL.md"}, {"name": "dependency-and-risk-management", "summary": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work", "trigger": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materialising unmanaged.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/dependency-and-risk-management/SKILL.md"}, {"name": "head-of-pmo", "summary": "The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance", "trigger": "The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/head-of-pmo/SKILL.md"}, {"name": "portfolio-governance", "summary": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things", "trigger": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/portfolio-governance/SKILL.md"}, {"name": "program-management", "summary": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving", "trigger": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/program-management/SKILL.md"}, {"name": "project-delivery", "summary": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips", "trigger": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/project-delivery/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "reviewer": false, "skills": [{"name": "chief-customer-officer", "summary": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product", "trigger": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/chief-customer-officer/SKILL.md"}, {"name": "escalation-management", "summary": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a r…", "trigger": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/escalation-management/SKILL.md"}, {"name": "self-service-and-knowledge", "summary": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability,…", "trigger": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md"}, {"name": "support-operations", "summary": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working", "trigger": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor quality, or decide what to automate.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/support-operations/SKILL.md"}, {"name": "voice-of-customer", "summary": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closi…", "trigger": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/voice-of-customer/SKILL.md"}]}, {"slug": "data-analytics", "title": "Data & Analytics", "exec": "CDO", "reviewer": false, "skills": [{"name": "ai-ml-governance", "summary": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or ret…", "trigger": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/ai-ml-governance/SKILL.md"}, {"name": "business-intelligence", "summary": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dash…", "trigger": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/business-intelligence/SKILL.md"}, {"name": "chief-data-officer", "summary": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top", "trigger": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/chief-data-officer/SKILL.md"}, {"name": "data-engineering", "summary": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery", "trigger": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-engineering/SKILL.md"}, {"name": "data-governance", "summary": "Establishes ownership, definitions, quality, access, and lineage for the organization's data", "trigger": "Establishes ownership, definitions, quality, access, and lineage for the organization's data. Use this when metrics disagree between teams, when nobody knows which dataset is authoritative, when setting up data ownership or access policy, when data quality is unreliable, or before opening a dataset to a wider audience.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-governance/SKILL.md"}, {"name": "data-modeling", "summary": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer an…", "trigger": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or diagnose why queries are slow, wrong, or impossible to write.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-modeling/SKILL.md"}]}, {"slug": "corporate-strategy", "title": "Corporate Strategy", "exec": "CSO", "reviewer": false, "skills": [{"name": "chief-strategy-officer", "summary": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and plann…", "trigger": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md"}, {"name": "mergers-and-acquisitions", "summary": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning", "trigger": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md"}, {"name": "portfolio-strategy", "summary": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence", "trigger": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide market entry or exit, structure a portfolio review, or when several initiatives compete for the same limited investment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md"}, {"name": "scenario-planning", "summary": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-te…", "trigger": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/scenario-planning/SKILL.md"}, {"name": "strategic-alliances", "summary": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM re…", "trigger": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/strategic-alliances/SKILL.md"}]}, {"slug": "people", "title": "People", "exec": "CHRO", "reviewer": false, "skills": [{"name": "benefits-and-leave", "summary": "Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them co…", "trigger": "Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/benefits-and-leave/SKILL.md"}, {"name": "chief-human-resources-officer", "summary": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations", "trigger": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/chief-human-resources-officer/SKILL.md"}, {"name": "compensation-and-leveling", "summary": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promoti…", "trigger": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/compensation-and-leveling/SKILL.md"}, {"name": "employee-relations", "summary": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly", "trigger": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employee-relations/SKILL.md"}, {"name": "hiring-and-interviewing", "summary": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself", "trigger": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/hiring-and-interviewing/SKILL.md"}, {"name": "learning-and-development", "summary": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility", "trigger": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/learning-and-development/SKILL.md"}, {"name": "onboarding-and-offboarding", "summary": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits", "trigger": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner or leaver.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/onboarding-and-offboarding/SKILL.md"}, {"name": "org-design", "summary": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the s…", "trigger": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/org-design/SKILL.md"}, {"name": "performance-management", "summary": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance", "trigger": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/performance-management/SKILL.md"}, {"name": "workforce-planning", "summary": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget", "trigger": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/workforce-planning/SKILL.md"}]}, {"slug": "legal-risk", "title": "Legal & Risk", "exec": "CLO / CCO", "reviewer": true, "skills": [{"name": "chief-legal-and-risk-officer", "summary": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness", "trigger": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit or certification, or when a plan may create obligations the business cannot meet. Also use to decide whether a risk should be accepted, mitigated, or refused.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/chief-legal-and-risk-officer/SKILL.md"}, {"name": "contract-review", "summary": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, prop…", "trigger": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback positions and approval thresholds, or assess exposure in terms already agreed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/contract-review/SKILL.md"}, {"name": "corporate-governance", "summary": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of au…", "trigger": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval authority, review insurance and continuity coverage, establish a retention policy, or work out where a responsibility belongs when it falls between functions.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/corporate-governance/SKILL.md"}, {"name": "enterprise-risk", "summary": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, a…", "trigger": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/enterprise-risk/SKILL.md"}, {"name": "privacy-and-data-protection", "summary": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject…", "trigger": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request arrives, when assessing exposure under GDPR or US state privacy laws, or when preparing for a privacy review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/privacy-and-data-protection/SKILL.md"}, {"name": "regulatory-compliance", "summary": "Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to re…", "trigger": "Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/regulatory-compliance/SKILL.md"}]}];
const grid = document.getElementById('grid');
const q = document.getElementById('q');
diff --git a/docs/org-chart.md b/docs/org-chart.md
index e5657ab..8d2419a 100644
--- a/docs/org-chart.md
+++ b/docs/org-chart.md
@@ -35,54 +35,59 @@ than into the function they oversee.
| `executive` | Office of the CEO | Chief Executive | 6 |
| `technology` | Technology | CTO / CIO | 18 |
| `security` | Security | CISO | 6 · reviewer-class |
-| `it-operations` | IT Operations | CIO | 7 |
+| `it-operations` | IT Operations | CIO | 8 |
| `product` | Product | CPO | 9 |
-| `marketing` | Marketing | CMO | 17 |
+| `marketing` | Marketing | CMO | 18 |
| `demand-generation` | Demand Generation | CMO | 11 |
| `revenue` | Revenue | CRO | 8 |
-| `finance` | Finance | CFO | 9 |
-| `operations` | Operations | COO | 8 |
-| `pmo` | Program Management Office | EPMO / COO | 6 |
+| `finance` | Finance | CFO | 10 |
+| `operations` | Operations | COO | 10 |
+| `pmo` | Program Management Office | EPMO / COO | 7 |
| `customer-experience` | Customer Experience | CCO | 5 |
| `data-analytics` | Data & Analytics | CDO | 6 |
| `corporate-strategy` | Corporate Strategy | CSO | 5 |
-| `people` | People | CHRO | 9 |
-| `legal-risk` | Legal & Risk | CLO / CCO | 5 · reviewer-class |
+| `people` | People | CHRO | 10 |
+| `legal-risk` | Legal & Risk | CLO / CCO | 6 · reviewer-class |
-16 departments, 135 skills.
+16 departments, 143 skills.
<!-- END GENERATED: departments -->
## Remaining gaps
+Validated against two public taxonomies rather than intuition: the **BLS Standard Occupational
+Classification** major groups 11-0000 (Management) and 13-0000 (Business and Financial Operations),
+and the shape of a cross-industry business. Every management occupation in 11-0000 that is not
+industry-specific now maps to a skill, and the gaps below are what remains.
+
### Tier 1 — worth building next
-**Legal depth.** Five skills. Missing `ip-and-licensing`, `regulatory-compliance`, and
-`audit-readiness` — the last pairing with `finance:internal-controls-and-audit`, which covers
-controls over financial reporting but not readiness for a wider audit.
+**Customer Experience depth.** Five skills, now the thinnest department. Missing
+`customer-onboarding`, `churn-and-recovery`, and `community`.
+
+**Legal depth.** Missing `ip-and-licensing` and `audit-readiness` — the latter pairing with
+`finance:internal-controls-and-audit`, which covers controls over financial reporting but not
+readiness for a wider audit.
+
+**Corporate Strategy depth.** Five skills. Missing `competitive-intelligence` and `market-entry`.
-**Customer Experience depth.** Five skills, the thinnest department. Missing `customer-onboarding`,
-`churn-and-recovery`, and `community`.
+**Product depth.** Nine skills, but weighted toward design and interface craft. Missing
+`product-discovery` and `roadmap-prioritization`.
-**Corporate Strategy depth.** Five skills. Missing `competitive-intelligence` and
-`market-entry`.
+### Tier 2 — real, but situational
-**Built since this list was written**, and removed from it: operations gained supply chain, quality
-management and capacity planning; finance gained revenue recognition, cash management as
-`treasury-and-liquidity`, investment appraisal as `capital-allocation`, and financial controls as
-`internal-controls-and-audit`; people gained performance management, employee relations, learning
-and development, and workforce planning. `procurement` was judged already covered by
-`operations:vendor-management` and `it-operations:it-asset-management` rather than needing its own
-skill.
+**Internal and executive communications.** `marketing:public-relations` covers earned media;
+nothing covers all-hands, change communication, or executive voice. `pmo:change-and-adoption`
+covers rollout communication only.
-### Tier 2
+**Investor relations.** Matters once there are investors, and not before.
-**Communications and Investor Relations.** `marketing:public-relations` covers earned media. No
-internal communications, executive communications, crisis communications, or IR. IR only matters
-once there are investors.
+**Labor and union relations.** SOC 13-1075. `people:employee-relations` covers individual
+grievances and investigations; collective bargaining is a different discipline. Weighted toward
+manufacturing, logistics and retail, so it belongs with the vertical packs rather than the core.
-**Product depth.** No dedicated `product-discovery`, `roadmap-prioritization`, or
-`pricing-experimentation` — the last overlapping `revenue:pricing-and-packaging`, so it may not
-warrant its own skill.
+**Industrial production management.** SOC 11-3051. `operations:quality-management` and
+`operations:capacity-and-demand-planning` cover the general disciplines; plant-floor management is
+vertical.
### Tier 3 — when the business needs them
@@ -93,6 +98,12 @@ warrant its own skill.
the CEO. Placing it under `executive` would reproduce the independence failure it exists to
prevent. It needs a reviewer-class agent no chief can overrule.
+### Deliberately out of scope
+
+The industry-specific management occupations in SOC 11-9000 — education, medical and health
+services, food service, lodging, gambling, funeral, agricultural and construction management — are
+correctly absent from a cross-industry core. They belong to the vertical variants in D8.
+
## Structural notes
**Reviewer independence is now modeled, not just described.** `security` and `legal-risk` each
diff --git a/plugins/finance/skills/tax/SKILL.md b/plugins/finance/skills/tax/SKILL.md
new file mode 100644
index 0000000..ddb8433
--- /dev/null
+++ b/plugins/finance/skills/tax/SKILL.md
@@ -0,0 +1,63 @@
+---
+name: tax
+description: Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.
+---
+
+# Tax
+
+Tax obligations are created by facts — where you sell, where people work, what you sell — not by
+decisions anyone consciously makes. The characteristic failure is discovering an obligation years
+after it began, with penalties and interest attached.
+
+**This structures the question and tells you what to ask. Tax is technical, jurisdiction-specific,
+and changes frequently. Positions on anything material belong with a qualified tax adviser or CPA,
+not a checklist.**
+
+## Nexus: the thing that creates obligations quietly
+
+Nexus is the connection that gives a jurisdiction the right to tax you. It is established by
+activities most companies do not think of as tax events:
+
+- **An employee working somewhere.** One remote hire in a new state commonly creates payroll
+ registration, income tax withholding, and often corporate income tax nexus.
+- **Economic activity without physical presence.** Since *Wayfair*, US states set sales-tax nexus on
+ revenue or transaction thresholds — a few hundred thousand dollars, or a couple of hundred
+ transactions, with the numbers differing by state.
+- **Inventory held somewhere**, including in a third-party fulfillment warehouse you never visit.
+- **Contractors, or attending trade shows**, in some jurisdictions.
+
+Review nexus whenever you hire in a new location, cross a revenue threshold, or change how you
+distribute. Registering late costs more than registering early, and voluntary disclosure programs
+exist precisely because this is so common.
+
+## Sales tax is about what you sell, not what you charge
+
+Taxability of software and services varies enormously by state: SaaS is taxable in some, exempt in
+others, and treated differently again if delivered with implementation services. The classification
+of your own product is a determination worth getting in writing and revisiting when packaging
+changes — see `revenue:pricing-and-packaging`, because bundling can change the answer.
+
+Exemption certificates for tax-exempt customers must be collected and kept current. In an audit,
+missing certificates mean you owe the tax you did not collect.
+
+## The calendar is most of the discipline
+
+Tax failures are usually administrative, not technical: a missed registration, a late filing, an
+estimated payment nobody scheduled. Maintain a calendar of every obligation by jurisdiction with an
+owner, and treat it as part of `finance:financial-reporting-and-close`.
+
+## Where it meets the rest of finance
+
+- `finance:financial-reporting-and-close` — tax provision and the deferred position
+- `finance:capital-allocation` — after-tax returns are the only ones that matter for a decision
+- `people:workforce-planning` — every hire in a new jurisdiction is a tax question before it is a
+ cost question
+- `revenue:revenue-recognition` — book and tax treatment diverge, and the difference is itself
+ something to track
+
+## Never
+
+- Assume no obligation because there is no office in a jurisdiction.
+- Treat your product's taxability as settled across states without a determination.
+- Sell into exempt customers without current exemption certificates.
+- Take a position on a material matter without a qualified adviser.
diff --git a/plugins/it-operations/skills/chief-information-officer/SKILL.md b/plugins/it-operations/skills/chief-information-officer/SKILL.md
new file mode 100644
index 0000000..e8dcbbe
--- /dev/null
+++ b/plugins/it-operations/skills/chief-information-officer/SKILL.md
@@ -0,0 +1,64 @@
+---
+name: chief-information-officer
+description: The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.
+---
+
+# Chief Information Officer
+
+The CIO runs the technology the company works *on*. The CTO runs the technology the company
+*sells*. Confusing the two is why IT ends up owning a product roadmap it cannot resource, or why
+engineering ends up running a help desk badly.
+
+## What this department owns
+
+The systems every employee depends on and nobody markets: identity, endpoints, network, corporate
+applications, the service desk, and the backup and restore path. Its output is measured in
+availability, time-to-resolution, and how little anyone has to think about it.
+
+- `it-operations:service-desk` — the front door, and the honest measure of whether any of this works
+- `it-operations:systems-administration` and `it-operations:network-administration` — the estate
+- `it-operations:endpoint-management` — the most exposed surface, because it leaves the building
+- `it-operations:identity-lifecycle-administration` — execution of joiner-mover-leaver
+- `it-operations:it-asset-management` — what you have, who has it, what it costs
+- `it-operations:backup-and-recovery` — the restore, tested rather than assumed
+
+## The boundaries that cause arguments
+
+State them once, in writing, and the recurring turf disputes stop:
+
+- **Security sets policy; IT executes it.** `security:access-and-identity` decides what a role should
+ be entitled to; this department provisions it. `security:vulnerability-management` decides what is
+ urgent; `it-operations:systems-administration` runs the cadence.
+- **Engineering owns the product estate; IT owns the corporate estate.**
+ `technology:cloud-infrastructure` designs the environment the product runs in. Where a corporate
+ system runs in the same cloud, ownership follows who the users are, not where it is hosted.
+- **Continuity objectives are the business's; the restore is IT's.**
+ `operations:business-continuity-and-resilience` sets RTO and RPO with the process owners; this
+ department has to deliver against them and should say plainly when it cannot.
+
+## Build, buy, or outsource
+
+Default to buy for anything that is not a differentiator. Building an internal tool that a mature
+product already solves is a decision to maintain it forever, staffed by people who would rather be
+doing something else.
+
+Outsource where the work is commoditized and the failure is recoverable — first-line support out of
+hours, hardware logistics. Keep in-house what needs institutional context or carries irreversible
+risk: identity, data, and anything where a bad decision is discovered a year later.
+
+## Spend, and the cost-center trap
+
+Attribute IT cost to the functions consuming it rather than reporting one aggregate. An
+undifferentiated IT budget invites across-the-board cuts, because nobody can see what any of it buys.
+
+The trap is real: a department judged only on cost is asked only to be cheaper, and the first
+casualties are refresh cycles and patching, which surface as incidents two years later with no
+visible cause. Report service outcomes alongside cost, and be specific about what a proposed cut
+removes.
+
+## Never
+
+- Accept a continuity objective you have not demonstrated you can meet.
+- Let identity policy and identity execution sit with the same reviewer.
+- Build an internal tool for a solved commodity problem.
+- Report IT cost without reporting what it delivered.
diff --git a/plugins/legal-risk/skills/regulatory-compliance/SKILL.md b/plugins/legal-risk/skills/regulatory-compliance/SKILL.md
new file mode 100644
index 0000000..ff492fc
--- /dev/null
+++ b/plugins/legal-risk/skills/regulatory-compliance/SKILL.md
@@ -0,0 +1,66 @@
+---
+name: regulatory-compliance
+description: Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.
+---
+
+# Regulatory compliance
+
+Compliance failures are rarely defiance. They are almost always an obligation nobody knew applied,
+in a jurisdiction nobody was watching, discovered by someone external.
+
+**This structures the work and names what to ask. Which regulations apply, and what they require,
+are legal determinations that vary by jurisdiction and change — they belong with qualified counsel.
+Nothing here substitutes for that.**
+
+## Start with an obligation map, not a framework
+
+The first question is not "are we SOC 2 compliant" but "what are we actually obliged to do, by
+whom, and what happens if we do not." Build the map from facts about the business:
+
+- **What you sell, and to whom.** Selling to regulated customers pulls their obligations onto you
+ through contract even when the regulation does not reach you directly.
+- **What data you hold.** Personal data, health data, payment data and children's data each carry
+ distinct regimes — see `legal-risk:privacy-and-data-protection`.
+- **Where you operate and where your customers are.** Obligations follow the customer more often
+ than companies expect.
+- **How you are funded and structured.** Public, regulated, or government-adjacent adds regimes.
+
+Distinguish three things that get conflated: **law** you must follow, **certifications** you choose
+to obtain commercially, and **contractual commitments** you signed. Only the first carries state
+enforcement; all three carry consequences.
+
+## Certifications are evidence, not compliance
+
+SOC 2, ISO 27001 and their equivalents demonstrate that controls exist and operate. They do not
+establish that you meet any legal obligation, and a clean report is not a defense to a regulator.
+
+Where they earn their cost is commercially — unblocking deals, as in the SOC 2 situation in
+`docs/USE-CASES.md`. Scope them to what the market asks for rather than to everything, since scope
+drives cost more than any other decision.
+
+## The program is monitoring, not documentation
+
+A compliance program that produces policies and stops is a shelf. What makes it real:
+
+- **An owner per obligation** — a named person, not a department.
+- **Controls that produce evidence as a by-product** of the work, rather than evidence assembled
+ before an audit. See `finance:internal-controls-and-audit` for the control design pattern.
+- **Monitoring that would detect failure** before an external party does, with the frequency matched
+ to how fast the obligation can be breached.
+- **Horizon scanning.** Regulation changes; a map built once is wrong within a year.
+
+## When a regulator arrives
+
+Respond promptly, accurately, and narrowly — answer what was asked. Route everything through counsel
+before it goes out, preserve records from the moment you are aware, and never let an informal
+conversation become an undocumented commitment.
+
+Findings get root-caused like any other failure. A remediation that consists of retraining people on
+a process that made the failure easy will produce the same finding next cycle.
+
+## Never
+
+- Treat a certification as evidence of legal compliance.
+- Build a compliance program without a named owner per obligation.
+- Assemble control evidence retrospectively for an audit.
+- Answer a regulator without counsel reviewing the response.
diff --git a/plugins/marketing/skills/events-and-field-marketing/SKILL.md b/plugins/marketing/skills/events-and-field-marketing/SKILL.md
new file mode 100644
index 0000000..c1f9d35
--- /dev/null
+++ b/plugins/marketing/skills/events-and-field-marketing/SKILL.md
@@ -0,0 +1,63 @@
+---
+name: events-and-field-marketing
+description: Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline.
+---
+
+# Events and field marketing
+
+Events are the most expensive marketing channel per contact and the easiest to spend badly on,
+because the outputs — booth traffic, badge scans, attendance — feel like results and are not.
+
+## Decide before you sponsor
+
+The question is never "should we be at this event" but "what specifically do we expect, and what is
+that worth." Answer three things first:
+
+- **Who is actually there.** Attendee seniority and function, not the headline number. A
+ ten-thousand-person event where forty of your buyers attend is a forty-person event.
+- **What the goal is**, and pick one: pipeline from new accounts, advancing deals already open,
+ customer retention and advocacy, or category presence. These need different booths, different
+ staff, and different follow-up, and an event asked to do all four does none.
+- **Total cost.** Sponsorship is often under half. Add booth build, shipping, travel, staff time out
+ of the field, and the content produced for it. The fully loaded figure changes decisions.
+
+Small, self-hosted, targeted formats — a dinner for fifteen right accounts, a focused workshop —
+routinely outperform large sponsorships per dollar for enterprise pipeline, and are unglamorous
+enough that they get proposed rarely.
+
+## Follow-up is where the money is lost
+
+Most event spend is wasted after the event, not during it. A scanned badge is not a lead, and the
+value decays in days.
+
+Agree before the event: who follows up, in what timeframe, with what message, and how those contacts
+are treated differently from inbound. Route it through `revenue:revenue-operations` so the tracking
+exists in advance, and hand the sequence to `demand-generation:lifecycle-messaging`.
+
+Score contacts honestly. Everyone who took a branded item is not a lead, and passing them to sales
+as if they were is how sales stops working the source at all.
+
+## Webinars and digital formats
+
+Same discipline, different economics. Registration is not attendance and attendance is not interest;
+the segment worth pursuing is people who stayed and asked something.
+
+The recording usually outperforms the live event over time, so plan the content as a durable asset —
+`marketing:content-strategy` and `marketing:video-content` — rather than as a one-time performance.
+
+## Measure with the attribution honesty the channel needs
+
+Events are structurally hard to attribute: they influence deals that close months later through
+paths no model captures cleanly. Overclaiming destroys the channel's credibility; refusing to
+measure destroys its funding.
+
+Track influenced pipeline with the assumption stated, alongside the honest direct-source number, and
+compare cost per opportunity against your other channels through
+`demand-generation:marketing-analytics`.
+
+## Never
+
+- Sponsor an event without a single stated goal.
+- Report badge scans as leads.
+- Leave follow-up ownership undecided until after the event.
+- Claim event-influenced revenue without stating the attribution assumption.
diff --git a/plugins/operations/skills/facilities-and-workplace/SKILL.md b/plugins/operations/skills/facilities-and-workplace/SKILL.md
new file mode 100644
index 0000000..05e70bf
--- /dev/null
+++ b/plugins/operations/skills/facilities-and-workplace/SKILL.md
@@ -0,0 +1,64 @@
+---
+name: facilities-and-workplace
+description: Runs the physical and hybrid workplace — space planning, leases, health and safety, office services, and the operational side of where people work. Use this to plan space, evaluate a lease or office move, set up a hybrid workplace, handle facilities incidents, or decide what office services are worth funding.
+---
+
+# Facilities and workplace
+
+Facilities is invisible when it works and is the loudest topic in the company when it does not. It
+is also, after payroll, frequently the largest fixed commitment a business makes.
+
+**Occupational health and safety, accessibility, and building compliance are legally regulated and
+vary by jurisdiction — and in the United States by state as well as federally. This structures the
+decision and names what to ask; it is not a substitute for qualified advice or a licensed
+inspection.**
+
+## Space follows how people actually work
+
+Plan from observed attendance, not from headcount or from policy. A hybrid organization with a
+three-day expectation does not need desks for everyone, and does need more of the rooms people
+compete for — small meeting spaces and focus rooms, which are chronically undersupplied because
+they are easy to convert into desks.
+
+Measure before committing: actual peak occupancy by day, room utilization, and what people leave
+the building to do. Most offices are simultaneously too large in aggregate and too small on
+Wednesday.
+
+## Leases are the commitment nobody models
+
+A lease is a multi-year fixed obligation signed on a headcount forecast that will be wrong. Treat it
+as the capital decision it is — `finance:capital-allocation` for the appraisal,
+`legal-risk:contract-review` for the terms.
+
+The terms that matter later: break clauses and what they cost, expansion and contraction rights,
+what "restore to original condition" obliges you to spend at exit, and who pays for what when the
+building fails. Dilapidations at lease end routinely surprise organizations that never read the
+clause.
+
+## Health, safety, and the duty of care
+
+The obligation follows the worker, not the building. Home workers, field staff and contractors are
+in scope in most jurisdictions, which organizations discover late.
+
+Keep the fundamentals current and evidenced: risk assessments, fire and evacuation, first aid,
+accident recording, and the statutory inspections the building requires. Evidence produced as a
+by-product of doing the work survives scrutiny; evidence assembled after an incident does not.
+
+Physical access control sits with `security:access-and-identity` for policy; site incidents that
+disrupt operations escalate to `operations:business-continuity-and-resilience`.
+
+## Office services, and what is worth funding
+
+Services are judged on whether they remove friction, not on generosity. Reliable connectivity,
+rooms that work on the first attempt, and somewhere to take a call beat perks that photograph well.
+
+Absorbs the administrative-services function — mail, reception, supplies, workplace vendors — which
+sits here rather than as a separate department, alongside `operations:vendor-management` for the
+suppliers delivering it.
+
+## Never
+
+- Size space from headcount rather than observed occupancy.
+- Sign a lease without modeling the exit and the dilapidations.
+- Treat health and safety as applying only to the office.
+- Fund visible perks while rooms and connectivity fail daily.
diff --git a/plugins/operations/skills/procurement-and-sourcing/SKILL.md b/plugins/operations/skills/procurement-and-sourcing/SKILL.md
new file mode 100644
index 0000000..9a1c186
--- /dev/null
+++ b/plugins/operations/skills/procurement-and-sourcing/SKILL.md
@@ -0,0 +1,63 @@
+---
+name: procurement-and-sourcing
+description: Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring uncontrolled spending under management.
+---
+
+# Procurement and sourcing
+
+This is everything before signature: deciding what to buy, from whom, and on what terms.
+`operations:vendor-management` takes over afterward — performance, renewals, exit.
+
+## Specify the need, not the product
+
+Most bad purchases are decided before any supplier is contacted, when a requirement is written as a
+product someone already wanted. Specify the outcome and the constraints; let suppliers propose how.
+
+Separate genuine requirements from preferences, and be honest about which is which. A requirements
+list that only one supplier satisfies is a purchase order with extra steps, and everyone involved
+knows it.
+
+Involve the people who will live with the choice. Procurement that optimizes price against a
+specification the users did not agree to produces a cheap thing nobody uses.
+
+## Competition is the leverage
+
+Price is set by the credible presence of an alternative, not by negotiating skill. The single most
+effective act in sourcing is having a real second option — and being willing to take it.
+
+Run a fair process: same information to every bidder, same questions answered for all, scoring
+agreed before responses arrive. Scoring invented afterward reliably rediscovers the preferred
+supplier.
+
+Where genuine competition is impossible — an incumbent with switching costs, a sole source —
+acknowledge it rather than staging a process. Then negotiate on the things still open: term length,
+renewal caps, service levels, exit assistance.
+
+## Total cost, not price
+
+The quoted figure is a fraction of what you will spend. Model implementation, integration, training,
+the internal effort to run it, and what leaving costs.
+
+Watch for cost that arrives later by design: per-seat pricing that grows with headcount, usage
+pricing with no cap, renewal uplifts, and support tiers that turn out to be mandatory. Ask what this
+costs in year three, and get the answer in the contract.
+
+## Category strategy
+
+Aggregate spend before negotiating it. The same category bought independently by four teams is four
+weak negotiating positions and usually four overlapping tools.
+
+Segment by leverage: high-spend commodity categories reward consolidation and hard negotiation;
+low-spend specialist ones are not worth the process cost. Concentrating everything on one supplier
+buys a discount and sells an exit — see `operations:business-continuity-and-resilience` before
+deciding that trade.
+
+Route the resulting terms through `legal-risk:contract-review`, and anything touching customer data
+through `legal-risk:privacy-and-data-protection` before signature rather than after.
+
+## Never
+
+- Write a requirement that only the preferred supplier can meet.
+- Agree scoring criteria after responses arrive.
+- Negotiate on price without modeling year-three total cost.
+- Consolidate a critical category onto one supplier without pricing the exit.
diff --git a/plugins/people/skills/benefits-and-leave/SKILL.md b/plugins/people/skills/benefits-and-leave/SKILL.md
new file mode 100644
index 0000000..06cc99b
--- /dev/null
+++ b/plugins/people/skills/benefits-and-leave/SKILL.md
@@ -0,0 +1,61 @@
+---
+name: benefits-and-leave
+description: Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
+---
+
+# Benefits and leave
+
+Benefits are the second largest people cost after salary and the one employees judge most directly.
+`people:compensation-and-leveling` covers pay bands and leveling; this covers everything else in the
+package.
+
+**Benefits and leave are heavily regulated and jurisdiction-specific — in the United States, ERISA,
+COBRA, ACA, FMLA and their state equivalents, with state family-leave and sick-leave laws differing
+substantially. Plan design and administration need a qualified benefits broker or employment
+counsel. This structures the decisions and names what to ask.**
+
+## Design for what people actually value
+
+Benefits budgets are routinely spent on things that survey well and are used rarely, while the
+things people quietly need are underfunded.
+
+The reliable pattern: health coverage quality, retirement match, and real time off dominate
+perceived value nearly everywhere. Beyond those, ask rather than assume — a young workforce and one
+with school-age children value very different things, and the difference is large enough to be worth
+measuring.
+
+Watch utilization. A benefit nobody uses is either badly communicated or badly chosen, and the two
+have different remedies.
+
+## Cost, and the renewal you should not sleepwalk
+
+Health costs rise faster than general inflation more or less every year, so a flat renewal is not
+the baseline — the baseline is an increase you must actively negotiate down or absorb by design.
+
+Start renewal months ahead, not weeks. Understand what drives your own experience rating, model plan
+design changes against employee impact, and market the plan periodically even when you intend to
+stay — a broker who knows you are not looking negotiates accordingly.
+
+Cost-shifting to employees is a pay cut delivered indirectly. It may be the right call; describe it
+honestly when you make it, because employees compute it correctly and describing it otherwise costs
+more trust than the money saved.
+
+## Leave: policy is the easy part
+
+Write policy that a manager can apply without calling HR for every case — eligibility, notice,
+documentation, pay treatment, and how it interacts with other leave types.
+
+The failures are in administration: leave running concurrently under multiple entitlements, return-
+to-work handled ad hoc, and accommodation requests treated as leave questions when they are legal
+ones. Route anything touching disability, pregnancy, or accommodation through counsel via
+`people:employee-relations`.
+
+Track leave centrally rather than in managers' memories. The organization that cannot say who is on
+what leave and until when is the one that mishandles a return.
+
+## Never
+
+- Change plan design without modeling the effect on the employees who use it most.
+- Enter a renewal without having tested the market recently.
+- Describe cost-shifting as a benefits enhancement.
+- Handle an accommodation request as a leave administration question.
diff --git a/plugins/pmo/skills/head-of-pmo/SKILL.md b/plugins/pmo/skills/head-of-pmo/SKILL.md
new file mode 100644
index 0000000..2e22938
--- /dev/null
+++ b/plugins/pmo/skills/head-of-pmo/SKILL.md
@@ -0,0 +1,62 @@
+---
+name: head-of-pmo
+description: The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
+---
+
+# Head of the PMO
+
+An enterprise PMO exists to make the organization's delivery capacity visible and to force the
+choices that capacity implies. It does not exist to collect status.
+
+## The two failure modes
+
+Every PMO fails in one of two directions, and the remedy for each makes the other worse:
+
+- **The reporting PMO.** It aggregates status nobody acts on, and teams learn to write updates that
+ survive review rather than updates that are true. Its meetings are attended and its findings
+ ignored. This is the common one.
+- **The controlling PMO.** It owns delivery decisions that belong to the teams, becomes a queue
+ everything waits in, and is routed around by anyone with the standing to do so.
+
+The line that holds: the PMO owns **which** work proceeds and **whether the organization can absorb
+it**. Teams own **how** the work gets done.
+
+## What it governs
+
+- `pmo:portfolio-governance` — intake, prioritization against real capacity, stage gates that can
+ stop things, and resource contention across projects
+- `pmo:program-management` and `pmo:project-delivery` — the delivery disciplines themselves
+- `pmo:dependency-and-risk-management` — the seams between teams, where programs actually fail
+- `pmo:benefits-realization` — whether the value claimed at approval ever appeared
+- `pmo:change-and-adoption` — whether anyone uses what was delivered
+
+Benefits and adoption are the two that make a PMO worth funding. A PMO that governs intake but never
+checks outcomes has only made the front door more expensive.
+
+## Reporting line, and why it matters
+
+The EPMO reports to the COO, not into any function whose work it governs. A PMO housed inside the
+largest delivery organization will, over time, prioritize that organization's work — not through bad
+faith but through proximity.
+
+It has no write surface over the departments it governs. Its authority is procedural: it runs the
+gate, it holds the capacity number, and it publishes what was decided.
+
+## Earning standing
+
+A PMO is obeyed when it is useful and circumvented when it is ceremony. What makes it useful:
+
+- **Say no visibly, and say why.** A gate that has never stopped anything is a gate nobody respects.
+- **Hold the capacity number and defend it.** The PMO is usually the only function that can see the
+ organization is committed past what it can deliver, and saying so is most of the job.
+- **Kill things.** Stopping a dead project releases capacity the whole portfolio needs, and
+ organizations are structurally bad at it — see `pmo:portfolio-governance`.
+- **Make reporting cost less than it returns.** Every status template is a tax on delivery. Ask for
+ what changes a decision and nothing else.
+
+## Never
+
+- Collect status that feeds no decision.
+- Take a delivery decision that belongs to the team doing the work.
+- Run a portfolio gate that has never stopped anything.
+- Let the PMO report into the function whose work it governs.