Agent Release Manager
ruvnet/ruflo
Agent skill for release-manager - invoke with $agent-release-manager
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.
$ npx skills add cbrock84/headcount --skill production-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount production-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .claude/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill production-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount production-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/verticals/industrial/skills/operations/production-management .agents/skills/production-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .agents/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill production-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount production-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/verticals/industrial/skills/operations/production-management .cursor/skills/production-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .cursor/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path verticals/industrial/skills/operations/production-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill production-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount production-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/verticals/industrial/skills/operations/production-management .gemini/skills/production-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .gemini/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount production-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill production-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/verticals/industrial/skills/operations/production-management .github/skills/production-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .github/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill production-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount production-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/verticals/industrial/skills/operations/production-management .opencode/skills/production-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "production-management" agent skill from https://github.com/cbrock84/headcount/tree/main/verticals/industrial/skills/operations/production-management into .opencode/skills/production-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "production-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
production-managementRuns 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. 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.
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 882 words, ~1,507 tokens.
.claude/skills/production-management/SKILL.md (or your agent's skills folder).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.
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:
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.
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.
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.
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:
Throughput at the constraint, plus on-time delivery, answers the business question. OEE answers the engineering question underneath it.
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.
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.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in verticals/industrial/skills/operations/production-management of cbrock84/headcount.
Open the folder on GitHubat commit 98d1c17
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Production Management this skillcbrock84/headcount | 2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Agent Release Managerruvnet/ruflo | 74k | 2 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Manage Schedulesasgeirtj/system_prompts_leaks | 69k | — | ~1.9k | Automated safety check: Pass | CC0-1.0 | |
| Scheduleasgeirtj/system_prompts_leaks | 69k | — | ~2.9k | Automated safety check: Pass | CC0-1.0 | |
| Scheduleasgeirtj/system_prompts_leaks | 69k | — | ~597 | Automated safety check: Pass | CC0-1.0 | |
| Schedule Managementaipoch/medical-research-skills | 1.9k | — | ~1.1k | Automated safety check: Pass | MIT |
ruvnet/ruflo
Agent skill for release-manager - invoke with $agent-release-manager
asgeirtj/system_prompts_leaks
Review a ChatGPT Space page and its schedules, recommend useful recurring work, and create, update, or remove scheduled automations.
asgeirtj/system_prompts_leaks
Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.
asgeirtj/system_prompts_leaks
Create or update a scheduled task that runs automatically. An agent skill from asgeirtj/system_prompts_leaks.
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.
Comfy-Org/workflow_templates
Manages releases for this repository: how version bumps, PyPI publishing, and GitHub releases work.
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…
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
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…
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.
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Production Management is instructions for the agent only.
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.
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.
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.
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.
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.
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.