New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Process Design

by cbrock84 in cbrock84/headcount

Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold.

MITAuto-check passed

Install Process Design

skills CLI
$ npx skills add cbrock84/headcount --skill process-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount process-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/operations/skills/process-design .claude/skills/process-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
process-design
GitHub stars
2k
Token cost
~832 tokens
SKILL.md length
467 words
Files
2 (incl. references)
Skills in repo
177
Repo updated
First seen
Licence
MIT

At a glance

Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold.

  • Works in 4 steps: Eliminate. Does this step need to exist?… → Simplify. Fewer handoffs, fewer… → Standardize. One way of doing it,… → …
  • SKILL.md covers Map what happens, not what is…, Find the real constraint, Redesign and Make it hold, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Process Design is an agent skill from cbrock84/headcount. 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.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

Example prompts

  • “/process-design”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Eliminate. Does this step need to exist? Many exist to catch a failure that a different fix
  2. Simplify. Fewer handoffs, fewer approvals, fewer systems. Every handoff is a place work
  3. Standardize. One way of doing it, written down, with the decision rules explicit.
  4. Automate. Last. Automating an unexamined process makes a bad process faster and much harder

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Process Design loads about 832 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~832
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 467 words, ~832 tokens.

Download SKILL.mdSave it as .claude/skills/process-design/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
process-design
description
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.

Process design

Map what happens, not what is supposed to happen

Follow a real instance end to end and record every step, handoff, wait, and rework loop. Talk to the people doing it, who will describe several steps that exist nowhere in the documentation and one or two that everyone has quietly stopped doing.

Then measure two things:

  • Touch time — how long the work actually takes.
  • Elapsed time — how long it takes to get through.

The gap between them is the process. In most broken processes, work is waiting more than ninety percent of the time, which means speeding up the work changes almost nothing. Attack the waits.

Find the real constraint

One step governs throughput. Improving anything else produces inventory in front of the constraint and no more output. Find it: the step with a queue in front of it.

Common constraints that are not the obvious step: a single approver, a specialist everything routes through, a system that only one team can access, and a batch cycle that makes everything wait for the weekly run.

Redesign

In this order, because the order is the leverage:

  1. Eliminate. Does this step need to exist? Many exist to catch a failure that a different fix would prevent entirely.
  2. Simplify. Fewer handoffs, fewer approvals, fewer systems. Every handoff is a place work stops.
  3. Standardize. One way of doing it, written down, with the decision rules explicit.
  4. Automate. Last. Automating an unexamined process makes a bad process faster and much harder to change.

Push approval to the lowest level that can be accountable, and set thresholds so routine cases do not queue behind exceptional ones.

Show full SKILL.md (191 more words)Show less

Make it hold

A documented process that relies on discipline degrades within a quarter. Build the control into the system: required fields, blocking gates, defaults that are correct, automated handoffs.

Never fix a recurring failure with a reminder. If people are forgetting a step, the system permits forgetting it. Fix that.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Redesign from the documented process. Map what people actually do first.
  • Optimize a step that is not the constraint. Everything you speed up ahead of it just queues.
  • Add an approval to prevent a failure that happened once.
  • Hand over a process with no owner and no measure. It reverts within a quarter.

Return contract

Current state with elapsed and touch time, the constraint and its evidence, the redesign, what it costs to implement, and the measure that will show it worked.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/operations/skills/process-design of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Process Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Process Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Process Design this skillcbrock84/headcount2k—~832Automated safety check: PassMIT
Fix PR Design Notesdifferent-ai/openwork24k—~824Automated safety check: PassCustom licence
Design Systemaffaan-m/ECC274k—~698Automated safety check: PassMIT
Design Guidepaperclipai/paperclip98k1 repos~3.1kAutomated safety check: PassMIT
Design Audit Against Rams' Principlesthedotmack/claude-mem97k—~4.6kAutomated safety check: PassApache-2.0
Figma Design to Codewarpdotdev/warp65k4 repos~2.9kAutomated safety check: PassAGPL-3.0

Similar skills

  • Fix PR Design Notes

    different-ai/openwork

    Reads the advisory design review attached to a pull request's screenshots, fixes the flagged UI problems in product code, and proves each note is gone.

    24k GitHub stars~824 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Design System

    affaan-m/ECC

    Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…

    274k GitHub stars~698 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    98k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed

  • Design Audit Against Rams' Principles

    thedotmack/claude-mem

    Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    97k GitHub stars~4.6k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed

  • Design Consultation

    garrytan/gstack

    Learns about your product, studies the landscape and writes a DESIGN.md with a full design system covering type, color, layout, spacing and motion.

    136k GitHub stars~15k tokensUpdated today
    Frontend & DesignAuto-check: notes

More from cbrock84/headcount

All 177 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    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…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    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.

    2k GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    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.

    2k GitHub stars~916 tokensUpdated 20 days ago
    Auto-check passed

  • AI Search Optimization

    cbrock84/headcount

    Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.

    2k GitHub stars~829 tokensUpdated 20 days ago
    Auto-check passed

Questions about Process Design

What does Process Design do?

Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Process Design is an agent skill from cbrock84/headcount. Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold.

How do I install Process Design in Claude Code?

Run `npx skills add cbrock84/headcount --skill process-design -a claude-code`. Or copy the skill folder (plugins/operations/skills/process-design in cbrock84/headcount) into .claude/skills/process-design in your project. Claude Code loads it when a task matches its description.

How do I install Process Design in Codex?

Run `npx skills add cbrock84/headcount --skill process-design -a codex`. Or copy the skill folder (plugins/operations/skills/process-design in cbrock84/headcount) into .agents/skills/process-design in your project. Codex loads it when a task matches its description.

Can I use Process Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill process-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-design, .gemini/skills/process-design, .github/skills/process-design and .opencode/skills/process-design in your project.

What does Process Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Process Design is instructions for the agent only.

Does Process Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Process Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Process Design use?

Process Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Process Design use?

About 832 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 348 tokens, read only when the agent opens those files.

What are the alternatives to Process Design?

Skills that share tags, products or a category with Process Design: Fix PR Design Notes (different-ai/openwork, 24k stars), Design System (affaan-m/ECC, 274k stars), Design Guide (paperclipai/paperclip, 98k stars) and Design Audit Against Rams' Principles (thedotmack/claude-mem, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Process Design?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,001 GitHub stars. The repository holds 177 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.