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.
HTML agent-marketplacechatgpt-pluginchatgpt-skillsclaude-codeclaude-code-pluginclaude-pluginclaude-skillsmcporganization
Fill security, legal-risk and technology gaps
Clauded41b3aeb19b9
diff --git a/README.md b/README.mdindex d3b7655..3f89b31 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="155 skills" src="https://img.shields.io/badge/skills-155-3F4B5B?style=flat-square">+ <img alt="160 skills" src="https://img.shields.io/badge/skills-160-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, 155 skills, searchable" src="docs/assets/org-chart-light.png" width="840">+ <img alt="The headcount org chart — 16 departments, 160 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, 155 skills in total.+a chief executive over 16 departments, 160 skills in total.Every department is an independently installable plugin, so a project loads only the functions itneeds rather than all of them at once.@@ -78,7 +78,7 @@ to as a subagent with its own exclusive write surface.</details><details>-<summary><b>Technology</b> (CTO / CIO) — 18 skills</summary>+<summary><b>Technology</b> (CTO / CIO) — 19 skills</summary>| Skill | What it does ||---|---|@@ -89,6 +89,7 @@ to as a subagent with its own exclusive write surface.| `cloud-infrastructure` | Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. || `code-review` | Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. || `completion-verification` | 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 rathe…. |+| `data-migration` | Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover,…. || `implementation-planning` | Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. || `observability-and-reliability` | Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. || `parallel-agent-delivery` | Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. |@@ -104,12 +105,14 @@ to as a subagent with its own exclusive write surface.</details><details>-<summary><b>Security</b> (CISO) — 6 skills · **reviewer-class**</summary>+<summary><b>Security</b> (CISO) — 8 skills · **reviewer-class**</summary>| Skill | What it does ||---|---|| `access-and-identity` | Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. || `chief-information-security-officer` | Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacc…. |+| `data-protection-and-encryption` | Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends a…. |+| `detection-and-monitoring` | Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on…. || `incident-response` | Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. || `security-architecture-review` | Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practic…. || `threat-modeling` | 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…. |@@ -333,14 +336,16 @@ to as a subagent with its own exclusive write surface.</details><details>-<summary><b>Legal & Risk</b> (CLO / CCO) — 6 skills · **reviewer-class**</summary>+<summary><b>Legal & Risk</b> (CLO / CCO) — 8 skills · **reviewer-class**</summary>| Skill | What it does ||---|---|| `chief-legal-and-risk-officer` | Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. || `contract-review` | Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions…. || `corporate-governance` | Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insura…. |+| `disputes-and-legal-holds` | Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion acro…. || `enterprise-risk` | Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing fo…. |+| `intellectual-property` | Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source lice…. || `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. |diff --git a/docs/assets/org-chart-dark.png b/docs/assets/org-chart-dark.pngindex be7838b..4ff4561 100644Binary files a/docs/assets/org-chart-dark.png and b/docs/assets/org-chart-dark.png differdiff --git a/docs/assets/org-chart-light.png b/docs/assets/org-chart-light.pngindex a7e8875..2315ff7 100644Binary files a/docs/assets/org-chart-light.png and b/docs/assets/org-chart-light.png differdiff --git a/docs/assets/social-card.html b/docs/assets/social-card.htmlindex 75993e1..000980e 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>155</b> skills <span class="sep">/</span>+ <b>160</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.pngindex caa7561..2ea6d6e 100644Binary files a/docs/assets/social-preview.png and b/docs/assets/social-preview.png differdiff --git a/docs/org-chart.html b/docs/org-chart.htmlindex 7e04d01..d6ccb2e 100644--- a/docs/org-chart.html+++ b/docs/org-chart.html@@ -251,7 +251,7 @@<div class="figures" id="figures"></div><div class="controls">- <input id="q" type="search" placeholder="Search 155 skills — try “threat”, “pricing”, “backup”…" autocomplete="off">+ <input id="q" type="search" placeholder="Search 160 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>@@ -286,7 +286,7 @@</div><script>-const DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "glyph": "M4 20h16M6 20V9l6-4 6 4v11M10 20v-5h4v5", "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", "glyph": "M9 8l-4 4 4 4M15 8l4 4-4 4", "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", "glyph": "M12 3.2l7 2.8v5.4c0 4.3-2.9 7.4-7 8.8-4.1-1.4-7-4.5-7-8.8V6z", "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", "glyph": "M3.5 5h17v10.5h-17zM9.5 20h5M12 15.5V20", "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": "cloud-administration", "summary": "Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, id…", "trigger": "Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get control of sprawling SaaS, cut a cloud bill, work out who owns an application nobody admits to buying, or decide what corporate workloads belong in cloud at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/cloud-administration/SKILL.md"}, {"name": "collaboration-platform-administration", "summary": "Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and ro…", "trigger": "Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/collaboration-platform-administration/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"}, {"name": "telephony-and-conferencing", "summary": "Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and i…", "trigger": "Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet emergency-calling requirements, port numbers without losing service, or work out why voice quality degrades only sometimes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/telephony-and-conferencing/SKILL.md"}, {"name": "virtualization-operations", "summary": "Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration…", "trigger": "Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set snapshot and template policy, or decide what stays virtualized and what moves to cloud.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/virtualization-operations/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "glyph": "M12 3.2l7.6 4.3v8.9L12 20.8l-7.6-4.4V7.5zM4.4 7.5l7.6 4.4 7.6-4.4M12 11.9v8.9", "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", "glyph": "M4 10v4h3l7 4V6l-7 4H4zM17.5 9.2a4 4 0 0 1 0 5.6", "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", "glyph": "M4 4.5h16l-6.2 7.2V19l-3.6 1.8v-9.1z", "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", "glyph": "M4 17.5l5.2-5.2 3.4 3.4L20 8.2M14.8 8.2H20v5.2", "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", "glyph": "M12 12m-8 0a8 8 0 1 0 16 0a8 8 0 1 0-16 0M12 7v10M14.6 9.4c0-1-1.2-1.7-2.6-1.7s-2.6.7-2.6 1.7 1.2 1.7 2.6 1.7 2.6.8 2.6 1.8-1.2 1.7-2.6 1.7-2.6-.7-2.6-1.7", "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": "capital-structure-and-covenants", "summary": "Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle r…", "trigger": "Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to evaluate a financing option, set an investment hurdle, check whether a planned decision will trip a covenant, or work out what a lender can do when one breaks.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-structure-and-covenants/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": "cost-accounting", "summary": "Establishes what something actually costs — fixed, variable and mixed cost behavior, absorption versus variable costing, job-order, process and activ…", "trigger": "Establishes what something actually costs — fixed, variable and mixed cost behavior, absorption versus variable costing, job-order, process and activity-based methods, breakeven and operating leverage, and price/volume/mix decomposition. Use this to set a price floor, explain why revenue or margin moved, decide make versus buy, judge whether a product line earns its place, or work out how an allocation basis is distorting a reported margin.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/cost-accounting/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": "financial-statement-analysis", "summary": "Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitabilit…", "trigger": "Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or target's financials, diagnose a deteriorating trend, explain a variance to someone who will act on it, or test whether an adjusted number is honest.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-statement-analysis/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", "glyph": "M4.2 12a7.8 7.8 0 0 1 13.3-5.5M19.8 12a7.8 7.8 0 0 1-13.3 5.5M18 3.4v3.6h-3.6M6 20.6V17h3.6", "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": "operating-cadence", "summary": "Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presente…", "trigger": "Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no decisions, work out where a recurring problem keeps failing to surface, or cut a review structure that has grown past what it informs.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/operating-cadence/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", "glyph": "M4 7h9M7.5 12h11M4 17h7", "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": "estimating-and-contingency", "summary": "Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenti…", "trigger": "Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one you have been handed, work out why estimates keep coming in low, or decide how much reserve a portfolio actually needs.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/estimating-and-contingency/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"}, {"name": "schedule-development-and-analysis", "summary": "Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and le…", "trigger": "Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/schedule-development-and-analysis/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "glyph": "M4 5h16v10.5H9.5L4 20z", "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", "glyph": "M4 20h16M7 20v-6M12 20V7M17 20v-9", "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", "glyph": "M12 12m-8 0a8 8 0 1 0 16 0a8 8 0 1 0-16 0M12 12m-3.4 0a3.4 3.4 0 1 0 6.8 0a3.4 3.4 0 1 0-6.8 0M12 12h.01", "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", "glyph": "M9 8.4m-3 0a3 3 0 1 0 6 0a3 3 0 1 0-6 0M3.4 20a5.6 5.6 0 0 1 11.2 0M17 9.4m-2.3 0a2.3 2.3 0 1 0 4.6 0a2.3 2.3 0 1 0-4.6 0M15.6 20a4.6 4.6 0 0 1 5-4.4", "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": "employment-compliance", "summary": "Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status,…", "trigger": "Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a contractor arrangement, respond to an accommodation request, work out what records to keep and for how long, or sanity-check a practice you inherited.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employment-compliance/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": "payroll-operations", "summary": "Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and…", "trigger": "Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and the deductions in it, multi-jurisdiction registration and tax filing, off-cycle payments and corrections, and the reconciliation to the general ledger. Use this to design or audit a payroll process, work out what happens when someone is paid wrong, or understand what changes when you hire in a new state or country.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/payroll-operations/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", "glyph": "M12 4.5v14.5M8 19h8M4 7.5h16M4 7.5l-2.4 5h4.8zM20 7.5l-2.4 5h4.8z", "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 DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "glyph": "M4 20h16M6 20V9l6-4 6 4v11M10 20v-5h4v5", "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", "glyph": "M9 8l-4 4 4 4M15 8l4 4-4 4", "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": "data-migration", "summary": "Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and paralle…", "trigger": "Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable. Use this to plan or run a migration, assess a migration plan someone else wrote, work out why a completed migration is producing wrong numbers, or size how long one will really take.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/data-migration/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", "glyph": "M12 3.2l7 2.8v5.4c0 4.3-2.9 7.4-7 8.8-4.1-1.4-7-4.5-7-8.8V6z", "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": "data-protection-and-encryption", "summary": "Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each act…", "trigger": "Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends against, managing keys and their rotation, handling secrets in applications and pipelines, minimizing and de-identifying, and deleting on purpose. Use this to design data protection for a system, assess an encryption claim, set up key or secret management, or work out what a stolen backup would actually expose.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/data-protection-and-encryption/SKILL.md"}, {"name": "detection-and-monitoring", "summary": "Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detectio…", "trigger": "Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/detection-and-monitoring/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", "glyph": "M3.5 5h17v10.5h-17zM9.5 20h5M12 15.5V20", "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": "cloud-administration", "summary": "Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, id…", "trigger": "Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get control of sprawling SaaS, cut a cloud bill, work out who owns an application nobody admits to buying, or decide what corporate workloads belong in cloud at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/cloud-administration/SKILL.md"}, {"name": "collaboration-platform-administration", "summary": "Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and ro…", "trigger": "Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/collaboration-platform-administration/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"}, {"name": "telephony-and-conferencing", "summary": "Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and i…", "trigger": "Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet emergency-calling requirements, port numbers without losing service, or work out why voice quality degrades only sometimes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/telephony-and-conferencing/SKILL.md"}, {"name": "virtualization-operations", "summary": "Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration…", "trigger": "Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set snapshot and template policy, or decide what stays virtualized and what moves to cloud.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/virtualization-operations/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "glyph": "M12 3.2l7.6 4.3v8.9L12 20.8l-7.6-4.4V7.5zM4.4 7.5l7.6 4.4 7.6-4.4M12 11.9v8.9", "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", "glyph": "M4 10v4h3l7 4V6l-7 4H4zM17.5 9.2a4 4 0 0 1 0 5.6", "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", "glyph": "M4 4.5h16l-6.2 7.2V19l-3.6 1.8v-9.1z", "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", "glyph": "M4 17.5l5.2-5.2 3.4 3.4L20 8.2M14.8 8.2H20v5.2", "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", "glyph": "M12 12m-8 0a8 8 0 1 0 16 0a8 8 0 1 0-16 0M12 7v10M14.6 9.4c0-1-1.2-1.7-2.6-1.7s-2.6.7-2.6 1.7 1.2 1.7 2.6 1.7 2.6.8 2.6 1.8-1.2 1.7-2.6 1.7-2.6-.7-2.6-1.7", "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": "capital-structure-and-covenants", "summary": "Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle r…", "trigger": "Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to evaluate a financing option, set an investment hurdle, check whether a planned decision will trip a covenant, or work out what a lender can do when one breaks.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-structure-and-covenants/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": "cost-accounting", "summary": "Establishes what something actually costs — fixed, variable and mixed cost behavior, absorption versus variable costing, job-order, process and activ…", "trigger": "Establishes what something actually costs — fixed, variable and mixed cost behavior, absorption versus variable costing, job-order, process and activity-based methods, breakeven and operating leverage, and price/volume/mix decomposition. Use this to set a price floor, explain why revenue or margin moved, decide make versus buy, judge whether a product line earns its place, or work out how an allocation basis is distorting a reported margin.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/cost-accounting/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": "financial-statement-analysis", "summary": "Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitabilit…", "trigger": "Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or target's financials, diagnose a deteriorating trend, explain a variance to someone who will act on it, or test whether an adjusted number is honest.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-statement-analysis/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", "glyph": "M4.2 12a7.8 7.8 0 0 1 13.3-5.5M19.8 12a7.8 7.8 0 0 1-13.3 5.5M18 3.4v3.6h-3.6M6 20.6V17h3.6", "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": "operating-cadence", "summary": "Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presente…", "trigger": "Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no decisions, work out where a recurring problem keeps failing to surface, or cut a review structure that has grown past what it informs.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/operating-cadence/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", "glyph": "M4 7h9M7.5 12h11M4 17h7", "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": "estimating-and-contingency", "summary": "Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenti…", "trigger": "Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one you have been handed, work out why estimates keep coming in low, or decide how much reserve a portfolio actually needs.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/estimating-and-contingency/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"}, {"name": "schedule-development-and-analysis", "summary": "Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and le…", "trigger": "Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/schedule-development-and-analysis/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "glyph": "M4 5h16v10.5H9.5L4 20z", "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", "glyph": "M4 20h16M7 20v-6M12 20V7M17 20v-9", "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", "glyph": "M12 12m-8 0a8 8 0 1 0 16 0a8 8 0 1 0-16 0M12 12m-3.4 0a3.4 3.4 0 1 0 6.8 0a3.4 3.4 0 1 0-6.8 0M12 12h.01", "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", "glyph": "M9 8.4m-3 0a3 3 0 1 0 6 0a3 3 0 1 0-6 0M3.4 20a5.6 5.6 0 0 1 11.2 0M17 9.4m-2.3 0a2.3 2.3 0 1 0 4.6 0a2.3 2.3 0 1 0-4.6 0M15.6 20a4.6 4.6 0 0 1 5-4.4", "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": "employment-compliance", "summary": "Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status,…", "trigger": "Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a contractor arrangement, respond to an accommodation request, work out what records to keep and for how long, or sanity-check a practice you inherited.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employment-compliance/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": "payroll-operations", "summary": "Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and…", "trigger": "Runs the pay cycle so it is right, on time, and provable — the calendar and cutoffs, what feeds pay from the HRIS and time systems, gross-to-net and the deductions in it, multi-jurisdiction registration and tax filing, off-cycle payments and corrections, and the reconciliation to the general ledger. Use this to design or audit a payroll process, work out what happens when someone is paid wrong, or understand what changes when you hire in a new state or country.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/payroll-operations/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", "glyph": "M12 4.5v14.5M8 19h8M4 7.5h16M4 7.5l-2.4 5h4.8zM20 7.5l-2.4 5h4.8z", "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": "disputes-and-legal-holds", "summary": "Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automati…", "trigger": "Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/disputes-and-legal-holds/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": "intellectual-property", "summary": "Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, o…", "trigger": "Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that you own work you paid for, decide how to handle a license obligation in a dependency, or respond to an infringement claim.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/intellectual-property/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.mdindex eab3e22..d64f49e 100644--- a/docs/org-chart.md+++ b/docs/org-chart.md@@ -33,8 +33,8 @@ than into the function they oversee.| Department | Function | Executive | Skills ||---|---|---|---|| `executive` | Office of the CEO | Chief Executive | 6 |-| `technology` | Technology | CTO / CIO | 18 |-| `security` | Security | CISO | 6 · reviewer-class |+| `technology` | Technology | CTO / CIO | 19 |+| `security` | Security | CISO | 8 · reviewer-class || `it-operations` | IT Operations | CIO | 12 || `product` | Product | CPO | 9 || `marketing` | Marketing | CMO | 18 |@@ -47,9 +47,9 @@ than into the function they oversee.| `data-analytics` | Data & Analytics | CDO | 6 || `corporate-strategy` | Corporate Strategy | CSO | 5 || `people` | People | CHRO | 12 |-| `legal-risk` | Legal & Risk | CLO / CCO | 6 · reviewer-class |+| `legal-risk` | Legal & Risk | CLO / CCO | 8 · reviewer-class |-16 departments, 155 skills.+16 departments, 160 skills.<!-- END GENERATED: departments -->## Remaining gapsdiff --git a/plugins/legal-risk/skills/disputes-and-legal-holds/SKILL.md b/plugins/legal-risk/skills/disputes-and-legal-holds/SKILL.mdnew file mode 100644index 0000000..0c59d6a--- /dev/null+++ b/plugins/legal-risk/skills/disputes-and-legal-holds/SKILL.md@@ -0,0 +1,76 @@+---+name: disputes-and-legal-holds+description: Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight.+---++# Disputes and legal holds++The decisions that determine how a dispute goes are made in the first week, usually by people who+do not know a dispute has started.++**This structures the operational response. Procedural obligations and their deadlines vary by+jurisdiction and forum — get counsel engaged early, and let them drive strategy.**++## Preservation attaches earlier than most people expect++The obligation to preserve begins when litigation is reasonably anticipated — which can be a demand+letter, a threat made in a meeting, a regulator's inquiry, or an internal complaint serious enough+that a claim is foreseeable. It does not wait for a filing.++**Destruction after that point is treated far more seriously than the underlying dispute.** Routine+automatic deletion continuing through a hold is the common version, and "it was our normal policy"+is not the defense people assume.++## Issue the hold in writing, and make it reach the systems++A hold has two halves and organizations routinely do only the first.++- **Notify the people.** Written, naming the matter in general terms, describing the categories of+ material to preserve, instructing recipients not to delete and not to discuss, and requiring+ acknowledgment. Identify custodians by what they touched, not by seniority.+- **Suspend the machinery.** Automatic deletion runs on schedules nobody remembers setting: mail+ retention, chat history expiry, ticket archival, log rotation, backup rotation, CRM purges,+ device wipe on offboarding. Each needs an explicit suspension for the affected scope.++**The systems half is where holds fail**, because the notice goes out and everyone assumes it was+sufficient. Keep a list of every system with an automatic deletion schedule so that the question is+answerable in an afternoon rather than a fortnight.++## Maintain the hold as a live thing++Re-notify periodically, add custodians as the matter develops, and cover departures — an employee+leaving under a hold means their mailbox, files and device do not follow the standard offboarding+path. Release the hold in writing when counsel says so, and only then.++## Privilege is easy to lose and cannot be recovered++Privilege protects legal advice, not facts and not business decisions dressed as legal ones.+Copying a lawyer onto a business discussion does not make it privileged; forwarding privileged+advice widely inside the organization can waive it.++Where an investigation is being run for the purpose of legal advice, structure it that way from the+start — directed by counsel, marked, and circulated narrowly. Retrofitting privilege afterward+generally fails.++## Manage counsel and cost deliberately++Agree scope, staffing, rates and a budget with checkpoints before work starts, and require early+written assessment of the realistic range of outcomes. Discovery is usually the largest cost and+the most controllable one — narrowing custodians and date ranges early matters more than any hourly+rate negotiation.++## Decide about settlement on expected cost, not on principle++Compare the realistic range of outcomes, weighted, against the full cost of continuing: fees,+management time, disruption, disclosure risk, and the effect on other matters. Management time is+the cost most consistently omitted and is often the largest.++Consider what a settlement signals to other potential claimants, and get releases that are broad+enough to actually end it.++## Never++- Wait for a filing before preserving.+- Send a hold notice without suspending the automatic deletion it depends on.+- Offboard someone under a hold through the standard process.+- Assume copying counsel on a message makes it privileged.diff --git a/plugins/legal-risk/skills/intellectual-property/SKILL.md b/plugins/legal-risk/skills/intellectual-property/SKILL.mdnew file mode 100644index 0000000..7afdebe--- /dev/null+++ b/plugins/legal-risk/skills/intellectual-property/SKILL.md@@ -0,0 +1,84 @@+---+name: intellectual-property+description: Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that you own work you paid for, decide how to handle a license obligation in a dependency, or respond to an infringement claim.+---++# Intellectual property++Most IP damage is done quietly and early — by a name adopted without a search, a contractor+agreement missing an assignment clause, or a dependency added without reading its license. All+three are cheap to prevent and expensive to unwind.++**This structures the questions and the recurring failure patterns. IP rights are jurisdictional,+deadline-driven and fact-specific — get qualified counsel before adopting a name, filing anything,+or responding to a claim.**++## The four rights protect different things and are not interchangeable++- **Trademark** protects a name or mark as an indicator of source, within classes of goods and+ services and within territories. Rights come from use and are strengthened by registration.+- **Copyright** protects expression, not ideas. It arises automatically on creation; registration+ matters mainly for what you can recover in a dispute.+- **Patent** protects an invention, in exchange for publishing it, and is defeated by your own+ prior public disclosure in many regimes. If patenting is plausible, file before you present,+ publish, or demonstrate.+- **Trade secret** protects information whose value depends on being secret, for as long as you+ actually keep it secret — which requires demonstrable measures, not just intent.++## Clear a name before you build on it++A search is cheap; a rebrand after launch is not, and the cost lands after you have printed+material, bought domains, and built recognition. Search registered marks in the classes and+territories you will operate in, and check for confusingly similar marks rather than exact matches.++Domain availability tells you nothing about trademark risk. Neither does the absence of a company+with that exact name.++## Establish ownership of work you paid for, in writing, before it starts++This is the most common and most avoidable failure in the whole area.++- **Employee work** is often owned by the employer by default, but the default varies by+ jurisdiction and by whether the work relates to the job.+- **Contractor and agency work is usually owned by the contractor** unless the agreement assigns it.+ A paid invoice is not an assignment. Logos, code, photography, and copy commissioned without an+ assignment clause routinely turn out to be licensed rather than owned — discovered during+ diligence, at the worst possible time.+- **Get assignment plus a waiver of moral rights where they apply**, and confirm the contractor had+ the right to assign anything they incorporated.++## Open-source obligations are license terms, not etiquette++Every dependency carries a license with conditions, and the conditions attach to distribution.++- **Permissive licenses** mostly require attribution and notice retention. Cheap, but not zero —+ the notices have to actually ship.+- **Strong copyleft** can require you to offer source for the combined work you distribute. Whether+ it reaches your code depends on how you combine and whether you distribute, and that analysis is+ worth doing before adoption rather than before a release.+- **Network copyleft** treats providing the software as a service as triggering the obligation,+ which surprises teams who assumed a hosted product avoids distribution entirely.++Maintain an inventory of dependencies and their licenses, generated rather than maintained by hand,+and gate new licenses at the point of adoption. Removing a dependency after it is embedded is a+project.++## Read the IP terms in agreements you sign++In customer contracts, watch for ownership of deliverables and of anything developed during the+engagement, broad license grants back to the customer, and feedback clauses assigning your+improvements. In tooling agreements, including AI services, check what rights are claimed over your+inputs and outputs and whether your content trains anything.++## Responding to a claim++Do not reply substantively before counsel sees it, do not admit anything, and preserve everything —+a claim letter triggers a preservation obligation immediately. Check whether insurance responds,+and check the indemnity you may hold from a supplier whose component is the actual subject.++## Never++- Adopt a name on the strength of domain availability.+- Commission work without a written assignment signed before the work starts.+- Add a dependency without knowing its license and what it requires on distribution.+- Respond to an infringement claim before counsel has seen it.diff --git a/plugins/security/skills/data-protection-and-encryption/SKILL.md b/plugins/security/skills/data-protection-and-encryption/SKILL.mdnew file mode 100644index 0000000..7ae64f6--- /dev/null+++ b/plugins/security/skills/data-protection-and-encryption/SKILL.md@@ -0,0 +1,80 @@+---+name: data-protection-and-encryption+description: Protects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends against, managing keys and their rotation, handling secrets in applications and pipelines, minimizing and de-identifying, and deleting on purpose. Use this to design data protection for a system, assess an encryption claim, set up key or secret management, or work out what a stolen backup would actually expose.+---++# Data protection and encryption++Perimeter and identity controls protect access to data. These controls protect the data when those+have already failed, which is the scenario worth designing for.++## Classify before you protect, because you cannot protect everything equally++A short scale beats a detailed one — three or four levels that people can apply without a manual.+What matters is that each level carries concrete handling rules: where it may be stored, who may+access it, whether it may leave the environment, and how long it is kept.++**Find it before you classify it.** Sensitive data is rarely only where the architecture says it+is: it accumulates in exports, analytics environments, test databases seeded from production,+support tickets, and log files.++## Know what each kind of encryption actually defends against++This is where claims get made loosely and expectations diverge from reality.++- **In transit** protects against interception on the network. Enforce it everywhere, including+ internal service-to-service traffic, and prefer a modern configuration over one accumulated+ over years.+- **At rest, provider-managed** protects against physical media theft and disk disposal. It does+ not protect against an application bug, a compromised credential, or an over-broad query — the+ storage layer decrypts transparently for anything with legitimate access. Full-disk encryption+ on a running server protects almost nothing about that server.+- **Application-level or field-level** protects specific fields from anything below the+ application, including database administrators and backups. It costs you searchability and+ indexing on those fields, which is a real design constraint rather than a footnote.++Choose deliberately. "Encrypted at rest" as a blanket assurance usually means the first of these,+and answers far less than the person asking believes.++## Keys are the whole control++Encryption moves the problem to key management; it does not remove it. A key stored beside the+data it protects provides documentation, not protection.++- **Use a managed key service or hardware-backed store.** Keys in configuration files, environment+ variables committed to a repository, or application code are the common real-world failure.+- **Separate duties** so the people who administer the data are not the people who administer the+ keys.+- **Plan rotation before you need it**, including how you re-encrypt existing data. Rotation nobody+ has practiced is a policy, and the moment you need it is after a suspected exposure.+- **Know what key destruction means.** Deleting a key makes the data unrecoverable, which is either+ a deletion mechanism you designed for or an outage you did not.++## Secrets are the credential case of the same problem++Application secrets — database passwords, API keys, service tokens — belong in a secret manager,+injected at runtime, scoped narrowly, and rotated on a schedule and on staff departure.++**Scan for committed secrets in CI and pre-commit**, and treat any secret that has ever reached a+repository as compromised. Removing the commit does not un-publish it; rotation is the only+remediation.++## Minimize, de-identify, and delete++The most reliable protection is not holding the data.++- **Collect what the purpose needs.** Every extra field is a permanent liability with no owner.+- **Do not seed test environments from production** without de-identification. This is one of the+ most common exposures and one of the easiest to fix.+- **Understand that removing names is not anonymization.** A combination of ordinary fields often+ re-identifies people; treat de-identified data as still sensitive unless someone has actually+ tested that it is not.+- **Delete on a schedule you can evidence**, and confirm deletion reaches backups, replicas,+ analytics copies and archives — where it usually does not.++## Never++- Describe data as encrypted without saying against which threat.+- Store a key or secret in the same place as the data or code it protects.+- Rotate credentials without confirming the old ones stop working.+- Copy production data into a test environment without de-identifying it first.diff --git a/plugins/security/skills/detection-and-monitoring/SKILL.md b/plugins/security/skills/detection-and-monitoring/SKILL.mdnew file mode 100644index 0000000..a13aba8--- /dev/null+++ b/plugins/security/skills/detection-and-monitoring/SKILL.md@@ -0,0 +1,82 @@+---+name: detection-and-monitoring+description: Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.+---++# Detection and monitoring++Incident response assumes someone noticed. Most organizations that respond well to incidents found+out from a customer, a vendor, or an extortion note, and the gap between compromise and discovery+is where nearly all of the damage accumulates.++## Decide what to log by asking what you would need afterward++Work backwards from the questions an investigation asks: who authenticated, from where, and what+did they then do. That points at a short list that matters far more than volume.++- **Identity events** — authentication success and failure, MFA changes, privilege grants, new+ API keys and tokens, consent grants to applications.+- **Endpoint process activity** — what ran, what spawned it, what it connected to.+- **Administrative actions** in the platforms that hold your data, especially permission and+ sharing changes.+- **Network egress** where you have it, and DNS, which is cheap and unusually informative.++**Retention decides whether you can investigate at all.** Intrusions are commonly discovered months+after entry, so logs kept for thirty days answer none of the useful questions. Split it: a short+hot window you can search fast, and a longer cold archive you can still reach.++## Centralize, and make the copy hard to erase++Logs stored only on the system that produced them are logs the attacker controls. Ship them off the+host as they are written, to a destination with different credentials from the systems it collects+from — otherwise one compromised administrator account ends both the intrusion and the evidence of+it.++## Write detections for behavior, not for events++A single event is almost never an incident. What distinguishes an attacker is a sequence:+authentication from a new location, followed by a mailbox rule creation, followed by a bulk+download.++- **Start from the techniques that actually apply to you.** Coverage is a property of your own+ estate, not of a vendor's rule count.+- **Detect the steps an attacker cannot skip** — persistence, privilege escalation, credential+ access, and exfiltration — rather than the tools they might use, which change.+- **High-signal detections available cheaply**: inbox rules that forward or delete externally, new+ federation or identity-provider trust, disabled logging, impossible travel on administrative+ accounts, and mass file access by a single principal.++Every detection needs a documented response. A detection that fires with no defined next step+becomes noise on its second occurrence.++## Tune ruthlessly, because alert fatigue is the real failure mode++An alert that is wrong most of the time trains people to close it without reading. The team stops+noticing, and the eventual real one closes the same way.++Measure the proportion of alerts that are actually actioned. Anything consistently below roughly+half is a tuning problem, and the fix is narrowing or suppressing the rule rather than adding+another analyst. A smaller number of trustworthy detections beats broad coverage nobody believes.++## Decide who is watching, and when++Coverage hours are an explicit decision with a cost. Business-hours monitoring means an intrusion+starting on Friday evening runs unobserved for two days, which is exactly why attacks are timed+that way. If you cannot staff around the clock, say so, and choose a small number of detections+that page a human at any hour rather than pretending the queue is monitored.++Outsourcing detection is legitimate and does not outsource the decision. The provider escalates;+someone inside still has to be reachable and authorized to disconnect something.++## Test that it would actually fire++Detection coverage is assumed far more often than it is verified. Run the behavior — a benign+version of the technique — and confirm the alert arrives, reaches a person, and carries enough+context to act on. Coverage claimed from a configuration page is not coverage.++## Never++- Retain logs for a window shorter than the time it typically takes to discover an intrusion.+- Store the only copy of a log on the system it describes.+- Ship a detection with no defined response.+- Claim coverage for a technique nobody has tested end to end.diff --git a/plugins/technology/skills/data-migration/SKILL.md b/plugins/technology/skills/data-migration/SKILL.mdnew file mode 100644index 0000000..818b286--- /dev/null+++ b/plugins/technology/skills/data-migration/SKILL.md@@ -0,0 +1,79 @@+---+name: data-migration+description: Moves data from one system to another without losing it or corrupting it — profiling the source before mapping, deciding between big-bang and parallel-run cutover, reconciling counts and values rather than assuming, handling the records that will not map cleanly, and planning a rollback that is actually executable. Use this to plan or run a migration, assess a migration plan someone else wrote, work out why a completed migration is producing wrong numbers, or size how long one will really take.+---++# Data migration++Migrations are estimated as a data-movement problem and turn out to be a data-quality problem. The+transfer is the easy part; discovering what the old system actually contains is where the time goes.++## Profile the source before you map anything++Look at the real data, not the schema and not what anyone tells you it contains. Every legacy+system has fields used for something other than their name, free-text where an enumeration was+intended, duplicates that both look canonical, and records predating a rule everyone believes has+always applied.++Count distinct values, null rates, format variance, and outliers on every field you intend to move.+This is the single highest-return activity in a migration and the one most often skipped in favor+of starting the mapping.++**Decide what not to move.** Migrating everything is the default and rarely the right answer.+Archive what has no live use and move a clean subset — it shrinks the mapping, the reconciliation,+and the cutover window all at once.++## Write the mapping down field by field, including the ugly parts++For each target field: source field, transformation, what happens when the source is empty, and+what happens when it does not fit. That last column is the one that decides how the migration goes.++**Records that will not map cleanly need a decision, not a default.** A row silently dropped, a+required field filled with a placeholder, or a truncated value is a defect discovered months later+by someone who trusted the number. Route exceptions to a list a human works through, and count+them.++## Rehearse on a full copy, more than once++A rehearsal on a sample proves the mapping compiles. A rehearsal on a full copy proves the timing,+finds the pathological records, and gives you a real number for the cutover window.++Expect several rehearsals. Each one should end with a reconciliation and a defect list, and the+last one should be clean and timed. Going into cutover having never completed a full run at+production volume means the cutover is the first full run.++## Choose the cutover style deliberately++- **Big-bang** — stop, migrate, start on the new system. Simplest to reason about, and the whole+ risk lands in one window. Viable when the window is affordable and rollback is real.+- **Parallel run** — both systems live, one authoritative. Safer and much more expensive, because+ something has to keep them in step and someone has to reconcile the divergence daily.+- **Phased** — by entity, region, or business unit. Reduces blast radius and creates the hardest+ problem in migration: records that reference each other across the boundary while it exists.++Whichever you pick, name the point of no return and what the rollback is on each side of it. **A+rollback that has never been executed is not a rollback**, and after the new system has taken live+writes, reverting means merging them back — which is a second migration nobody planned.++## Reconcile on counts and on values++Row counts alone catch a truncated load and nothing else. Reconcile control totals for anything+financial, distributions for key fields, and a sample compared record by record. Then have the+people who use the data check the records they know by heart — they find things no query will.++Reconcile again a week after cutover. Problems in the ongoing integrations that replaced the+migration usually show up then rather than on the day.++## Plan for the long tail++Migrations are declared done and then produce findings for months. Keep the source system readable+for longer than feels necessary, keep the mapping and the exception lists, and keep someone+assigned. The alternative is a question about a historical record that nobody can answer because+the old system was decommissioned on schedule.++## Never++- Map from the schema rather than from the data.+- Let a record fail to map and be dropped without landing on a list someone works.+- Cut over without a full-volume rehearsal that completed and reconciled.+- Decommission the source system before the reconciliation window has closed.