Agent skill

Production Management

by cbrock84 in cbrock84/headcount

Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree.

MITAuto-check passed

Install Production Management

skills CLI
$ npx skills add cbrock84/headcount --skill production-management -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount production-management --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/verticals/industrial/skills/operations/production-management .claude/skills/production-management && 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
production-management
GitHub stars
2k
Token cost
~1.5k tokens
SKILL.md length
882 words
Files
1
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree.

  • SKILL.md covers Sequence is the decision, not…, Work in process is the lead time, Changeover is capacity you can… and OEE tells you where, not whether, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Production Management is an agent skill from cbrock84/headcount. Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree. Use this to build or fix a production schedule, decide what to run next, diagnose why lead times are growing while machines look busy, set up OEE or throughput measurement, or choose between make-to-stock and make-to-order for a product line.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

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

  • “/production-management”

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

Production Management loads about 1.5k tokens when it runs. Until then it costs about 111 tokens; SKILL.md has 882 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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). 882 words, ~1,507 tokens.

Download SKILL.mdSave it as .claude/skills/production-management/SKILL.md (or your agent's skills folder).
name
production-management
description
Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree. Use this to build or fix a production schedule, decide what to run next, diagnose why lead times are growing while machines look busy, set up OEE or throughput measurement, or choose between make-to-stock and make-to-order for a product line.

Production management

The schedule is a promise made to a customer using capacity you do not fully control. Most plants that miss dates are not short of machine hours. They are running a sequence that maximizes utilization on each machine and no one is accountable for the order.

Sequence is the decision, not the loading

Loading answers how much work a resource has. Sequence answers what the customer gets and when, and it is the part usually left to whoever is standing at the machine.

Two sequences with identical total hours produce very different outcomes:

  • Grouped by setup — run everything in the same color, material or die together. Maximizes machine output, and pushes any order that does not fit the current group to the back.
  • Grouped by due date — run what is owed soonest. Protects dates, and pays for it in changeovers.

Neither is correct in general. What is not acceptable is the choice being made implicitly, shift by shift, by someone with no view of the order book. Decide the rule, write it down, and state what overrides it — because something always will, and an unstated override is how a schedule quietly stops meaning anything.

Work in process is the lead time

Little's Law is the whole of it: lead time equals work in process divided by throughput. Releasing more work into a plant that is already full does not make anything come out sooner. It lengthens every job on the floor, including the one that was on time.

The practical consequence is that release is a control and most plants do not use it as one. Work is released when the order arrives or when the paperwork clears, and the floor absorbs it. Capping releases against a work-in-process target feels like doing less and shortens quoted lead times measurably.

The tell that release is uncontrolled: expediting works. If pushing a job to the front reliably gets it out, there is enough queue on the floor to hide the cost, and someone else's date moved.

Changeover is capacity you can buy back

Setup time is usually treated as fixed, so the response to losing capacity to it is longer runs, which raises inventory and lengthens lead times for everything else.

Attack the setup instead. Separate the work that can be done while the machine is still running — staging material, pre-setting tooling, moving the next die to the press — from the work that genuinely requires it stopped. Most first attempts find that a third or more of the setup did not need the machine idle. That recovered time is real capacity, and it costs nothing.

The second-order effect matters more than the recovered hours: cheaper changeovers make small runs viable, which makes due-date sequencing affordable, which is what protects the promise.

OEE tells you where, not whether

Overall equipment effectiveness multiplies availability, performance and quality. Its value is the decomposition — a line at 60% for three different reasons needs three different fixes.

Two ways it misleads:

  • On a non-bottleneck it is noise. Improving OEE on a resource that is not constraining output produces inventory, not throughput. Measure it where the constraint is.
  • It rewards running. A line kept running to protect the number, making parts nobody ordered, scores well. Pair it with schedule adherence or it will quietly optimize for the wrong thing.

Throughput at the constraint, plus on-time delivery, answers the business question. OEE answers the engineering question underneath it.

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

Make-to-stock and make-to-order are a lead-time decision

The choice is between holding inventory and holding the customer waiting, and it is made per product family rather than per plant.

Make-to-stock where demand is predictable, the item is standard, and the customer's tolerance for waiting is shorter than the production lead time. Make-to-order where variety is high, the item carries customer-specific content, or obsolescence risk is real.

The hybrid is usually the right answer and rarely stated: hold the common part as stock, finish to order. That moves the decoupling point as late as possible, which is where inventory is cheapest and most flexible. operations:capacity-and-demand-planning holds the demand side of this decision.

Tooling

Scheduling and shop-floor execution is where an ERP is either doing the work or being worked around. SAP, Oracle NetSuite, Epicor Kinetic, Infor CloudSuite Industrial, Odoo and similar carry the order book, routings and material availability, and the schedule should come from the same system that knows whether the material is there.

Finite-capacity scheduling — PlanetTogether, Preactor, Opcenter APS and similar — earns its place where sequence-dependent setups, shared tooling or constrained labor make the ERP's infinite-capacity plan fiction. Below that complexity a well-maintained spreadsheet with a stated sequencing rule beats a scheduler nobody trusts.

Machine-level data collection sits underneath OEE. At scale, a manufacturing execution system; below it, a tablet at the line and an honest downtime reason code list are enough to find the top three causes, which is all the first year needs.

Never

  • Release work into a full plant because the order arrived.
  • Let sequence be decided at the machine by whoever is standing there.
  • Improve utilization on a resource that is not the constraint and call it capacity.
  • Quote a lead time from routed hours rather than from observed work in process.
  • Report a schedule as met after the dates were moved to match what shipped.

© 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

Just SKILL.md in verticals/industrial/skills/operations/production-management of cbrock84/headcount.

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Production Management 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.

Production Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Production Management this skillcbrock84/headcount2k—~1.5kAutomated safety check: PassMIT
Agent Release Managerruvnet/ruflo74k2 repos~3.1kAutomated safety check: PassMIT
Manage Schedulesasgeirtj/system_prompts_leaks69k—~1.9kAutomated safety check: PassCC0-1.0
Scheduleasgeirtj/system_prompts_leaks69k—~2.9kAutomated safety check: PassCC0-1.0
Scheduleasgeirtj/system_prompts_leaks69k—~597Automated safety check: PassCC0-1.0
Schedule Managementaipoch/medical-research-skills1.9k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Agent skill for release-manager - invoke with $agent-release-manager

    74k GitHub starsUsed in 2 repos~3.1k tokens
    DevelopmentAuto-check passed
  • Manage Schedules

    asgeirtj/system_prompts_leaks

    Review a ChatGPT Space page and its schedules, recommend useful recurring work, and create, update, or remove scheduled automations.

    69k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Schedule

    asgeirtj/system_prompts_leaks

    Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.

    69k GitHub stars~2.9k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Schedule

    asgeirtj/system_prompts_leaks

    Create or update a scheduled task that runs automatically. An agent skill from asgeirtj/system_prompts_leaks.

    69k GitHub stars~597 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Schedule Management

    aipoch/medical-research-skills

    Local schedule management for adding events, tracking deadlines, generating reminders, and detecting time conflicts when users need offline scheduling with optional popup notifications.

    1.9k GitHub stars~1.1k tokensUpdated 24 days ago
    Data & AnalyticsAuto-check passed
  • Managing Releases

    Comfy-Org/workflow_templates

    Manages releases for this repository: how version bumps, PyPI publishing, and GitHub releases work.

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

More from cbrock84/headcount

All 178 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 23 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 23 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 23 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 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 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 23 days ago
    Auto-check passed

Questions about Production Management

What does Production Management do?

Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree. Production Management is an agent skill from cbrock84/headcount. Runs the production schedule — sequencing and releasing work, managing work in process and changeovers, and holding the promised date when the floor and the order book disagree.

How do I install Production Management in Claude Code?

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

How do I install Production Management in Codex?

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

Can I use Production Management 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 production-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/production-management, .gemini/skills/production-management, .github/skills/production-management and .opencode/skills/production-management in your project.

What does Production Management need to run?

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

Does Production Management 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 Production Management 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 Production Management use?

Production Management 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 Production Management use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Production Management?

Skills that share tags, products or a category with Production Management: Agent Release Manager (ruvnet/ruflo, 74k stars), Manage Schedules (asgeirtj/system_prompts_leaks, 69k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars) and Schedule (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Production Management?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 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.