Plan
codewhale-hq/Codewhale
Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification.
Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving.
MITAuto-check passed
Install Program Management
$ npx skills add cbrock84/headcount --skill program-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount program-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/plugins/pmo/skills/program-management .claude/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .claude/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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/plugins/pmo/skills/program-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 program-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount program-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/plugins/pmo/skills/program-management .agents/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .agents/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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 program-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount program-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/plugins/pmo/skills/program-management .cursor/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .cursor/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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 plugins/pmo/skills/program-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 program-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount program-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/plugins/pmo/skills/program-management .gemini/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .gemini/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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 program-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 program-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/plugins/pmo/skills/program-management .github/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .github/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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 program-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 program-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/plugins/pmo/skills/program-management .opencode/skills/program-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 "program-management" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/program-management into .opencode/skills/program-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "program-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.
Facts
- Skill name
program-management- GitHub stars
- 2k
- Token cost
- ~757 tokens
- SKILL.md length
- 417 words
- Files
- 2 (incl. references)
- Skills in repo
- 175
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving.
- SKILL.md covers Set up, Sequencing, Status that is worth reading and When it slips, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Program Management is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 760 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
- “Use the program-management skill to plan and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the…”
- “/program-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
Program Management loads about 757 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 417 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.
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). 417 words, ~757 tokens.
Download SKILL.mdSave it as
.claude/skills/program-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- program-management
- description
- 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.
Program management
Programs fail at the seams between teams, not inside them. The job is the seams.
Set up
- One outcome, stated as a business result with a date. Programs with several equal objectives have none.
- A named accountable owner — one person, not a committee. The program manager drives; the owner decides.
- Scope written as inclusions and exclusions. The exclusions do the work; unwritten exclusions return as assumptions.
- Dependencies mapped and agreed by the teams that owe them, with dates they have actually committed to. A dependency in your plan that the owning team has not agreed to is a wish.
Sequencing
Order by dependency and risk, not by team convenience. Front-load the things that could invalidate the plan — the technical unknown, the vendor decision, the approval that might not come. Discovering in month four that the plan was impossible is the characteristic program failure.
Build in slack at integration points, not at the end. End-loaded buffer gets consumed early and silently.
Status that is worth reading
Three things, every time: are we on track for the date, what changed since last time, and what decision or unblock is needed. Everything else is appendix.
Track status against committed dates, not effort. "80% complete" is not information; "the integration is done, the migration starts Monday, the sign-off is the risk" is.
Escalate early and specifically. An escalation naming the decision needed and the date it is needed by gets resolved; a general statement of concern gets acknowledged and nothing happens.
Show full SKILL.md (168 more words)Show less
When it slips
Establish whether it is a scope problem, a capacity problem, or a dependency problem — the remedies are entirely different and applying the wrong one makes it worse.
Then present options with consequences: cut scope (name what), extend (say by how much and what else is affected), or add capacity (which rarely helps late, and often hurts).
Re-baseline once, visibly, rather than slipping a week at a time. Serial small slips destroy credibility far faster than one honest reset.
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
- Report green on a program with an unresolved blocker.
- Accept a dependency date the owning team has not confirmed.
- Add people to a late program and assume it accelerates.
© 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/pmo/skills/program-management of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Program 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 |
|---|---|---|---|---|---|---|
| Program Management this skillcbrock84/headcount | 2k | — | ~757 | Automated safety check: Pass | MIT | |
| Plancodewhale-hq/Codewhale | 41k | — | ~213 | Automated safety check: Pass | MIT | |
| Planningn8n-io/n8n | 207k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Planasgeirtj/system_prompts_leaks | 69k | — | ~5.1k | Automated safety check: Pass | CC0-1.0 | |
| Review Planpenpot/penpot | 61k | — | ~841 | Automated safety check: Pass | MPL-2.0 | |
| Make A Planpenpot/penpot | 61k | — | ~1.6k | Automated safety check: Pass | MPL-2.0 |
Similar skills
- Official
Planning
n8n-io/n8n
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first.
Plan
asgeirtj/system_prompts_leaks
On an explicit planning request, always call readskill for this skill before answering.
Review Plan
penpot/penpot
Plan review flow — evaluate an implementation plan before it is executed, delegating the review to a subagent that follows the plan-review-criteria skill.
Make A Plan
penpot/penpot
Planning flow — research the subject of this session, produce an implementation plan with the planner skill, resolve open questions with the user in plain language, and save the final plan to…
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
More from cbrock84/headcount
All 175 skills in this repoAgent 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…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
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…
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.
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.
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.
Questions about Program Management
What does Program Management do?
Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Program Management is an agent skill from cbrock84/headcount. Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving.
How do I install Program Management in Claude Code?
Run `npx skills add cbrock84/headcount --skill program-management -a claude-code`. Or copy the skill folder (plugins/pmo/skills/program-management in cbrock84/headcount) into .claude/skills/program-management in your project. Claude Code loads it when a task matches its description.
How do I install Program Management in Codex?
Run `npx skills add cbrock84/headcount --skill program-management -a codex`. Or copy the skill folder (plugins/pmo/skills/program-management in cbrock84/headcount) into .agents/skills/program-management in your project. Codex loads it when a task matches its description.
Can I use Program 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 program-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/program-management, .gemini/skills/program-management, .github/skills/program-management and .opencode/skills/program-management in your project.
What does Program Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Program Management is instructions for the agent only.
Does Program 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 Program 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 Program Management use?
Program 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 Program Management use?
About 757 tokens (SKILL.md is roughly 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 331 tokens, read only when the agent opens those files.
What are the alternatives to Program Management?
Skills that share tags, products or a category with Program Management: Plan (codewhale-hq/Codewhale, 41k stars), Planning (n8n-io/n8n, 207k stars), Plan (asgeirtj/system_prompts_leaks, 69k stars) and Review Plan (penpot/penpot, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Program Management?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,007 GitHub stars. The repository holds 175 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.