Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things.
Install Portfolio Governance
$ npx skills add cbrock84/headcount --skill portfolio-governance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount portfolio-governance --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/portfolio-governance .claude/skills/portfolio-governance && 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 "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .claude/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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/portfolio-governanceType 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 portfolio-governance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount portfolio-governance --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/portfolio-governance .agents/skills/portfolio-governance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .agents/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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 portfolio-governance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount portfolio-governance --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/portfolio-governance .cursor/skills/portfolio-governance && 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 "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .cursor/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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/portfolio-governance--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 portfolio-governance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount portfolio-governance --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/portfolio-governance .gemini/skills/portfolio-governance && 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 "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .gemini/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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 portfolio-governanceInstalls 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 portfolio-governance -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/portfolio-governance .github/skills/portfolio-governance && 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 "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .github/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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 portfolio-governance -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 portfolio-governance --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/portfolio-governance .opencode/skills/portfolio-governance && 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 "portfolio-governance" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/portfolio-governance into .opencode/skills/portfolio-governance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "portfolio-governance", 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
portfolio-governance- GitHub stars
- 2k
- Token cost
- ~935 tokens
- SKILL.md length
- 523 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things.
- Tasks that involve Prioritization frameworks
- SKILL.md covers Intake as a real gate, Prioritize against capacity,…, Stage gates that can say no and Stopping is the hardest and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Portfolio Governance is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 940 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`).
It sits in Product & Project Management, covering Prioritization frameworks. 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.
When your agent uses it
- Tasks that involve Prioritization frameworks
Example prompts
- “Use the portfolio-governance skill to govern the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things”
- “/portfolio-governance”
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
Portfolio Governance loads about 935 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 523 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). 523 words, ~935 tokens.
Download SKILL.mdSave it as
.claude/skills/portfolio-governance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- portfolio-governance
- description
- 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.
Portfolio governance
The portfolio question is not which projects are good. Most proposed work is defensible in isolation. It is which projects the organization can actually finish, given that finishing is what produces value and starting produces none.
Intake as a real gate
Without a single front door, work enters through relationships and volume, and the portfolio becomes the sum of who asked most persistently.
Require the same minimum from every proposal regardless of who is asking: the outcome sought, the evidence it matters, a rough size, the accountable owner, and what will not happen if it proceeds. That last one is the honest part — capacity is fixed, so approving anything is declining something else, whether or not the decline is ever stated.
Prioritize against capacity, not against merit
Ranking by value produces a list where everything above the line is approved and the line is
imaginary. Prioritization only means something when the cut is made at real, measured delivery
capacity — see operations:capacity-and-demand-planning for the throughput side.
Limit work in progress. An organization running twenty concurrent initiatives with capacity for eight does not deliver twenty slowly; it delivers roughly eight, considerably later, with the overhead of context-switching across all twenty. Fewer things, finished, is faster in wall-clock terms — which is counter-intuitive and is why the discipline requires governance rather than good intentions.
Stage gates that can say no
A gate whose only outcome is approval is a status meeting. Each gate must be able to stop, pause, or redirect, and needs a named decision-maker with the authority to do it.
Gate on what has been learned since the last one, not on whether documentation was produced. The useful question is whether the case still holds now that more is known — and it frequently does not, which is exactly the information the gate exists to surface.
Show full SKILL.md (218 more words)Show less
Stopping is the hardest and most valuable act
Organizations start well and stop badly. Sunk cost, sponsor prestige and the discomfort of admitting error keep dead projects consuming capacity that the whole portfolio needs.
Make stopping a normal, non-punitive outcome. Where stopping is treated as failure, projects are never stopped — they are quietly starved, which is the same cost with none of the released capacity and no decision anyone can point to.
Resource contention
Contention across projects is resolved here, at the portfolio, not by the projects negotiating among themselves. Left to negotiation, the outcome reflects seniority of the sponsors rather than value to the organization.
Watch for the same scarce specialist appearing on the critical path of several initiatives — the most common invisible cause of portfolio-wide slippage.
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
- Approve work without naming what it displaces.
- Set a priority order without a line drawn at real capacity.
- Run a gate that cannot stop anything.
- Starve a project instead of stopping it.
© 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/portfolio-governance of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Portfolio Governance 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 |
|---|---|---|---|---|---|---|
| Portfolio Governance this skillcbrock84/headcount | 2k | — | ~935 | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Prioritization Framework Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.2k | Automated safety check: Pass | Custom licence | |
| Strategic Roadmap Planningdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.7k | Automated safety check: Pass | Custom licence | |
| Idea Validatoraakashg/pm-claude-skills | 112 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Triagejoa23/linear-cli | 144 | — | ~699 | Automated safety check: Pass | MIT |
Similar skills
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
Idea Validator
aakashg/pm-claude-skills
A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.
Triage
joa23/linear-cli
Triage and prioritize Linear backlog issues using the linear CLI.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
More from cbrock84/headcount
All 178 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 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.
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.
Related
Categories
Questions about Portfolio Governance
What does Portfolio Governance do?
Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Portfolio Governance is an agent skill from cbrock84/headcount. Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things.
When should I use Portfolio Governance?
Portfolio Governance fits situations like: tasks that involve Prioritization frameworks.
How do I install Portfolio Governance in Claude Code?
Run `npx skills add cbrock84/headcount --skill portfolio-governance -a claude-code`. Or copy the skill folder (plugins/pmo/skills/portfolio-governance in cbrock84/headcount) into .claude/skills/portfolio-governance in your project. Claude Code loads it when a task matches its description.
How do I install Portfolio Governance in Codex?
Run `npx skills add cbrock84/headcount --skill portfolio-governance -a codex`. Or copy the skill folder (plugins/pmo/skills/portfolio-governance in cbrock84/headcount) into .agents/skills/portfolio-governance in your project. Codex loads it when a task matches its description.
Can I use Portfolio Governance 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 portfolio-governance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/portfolio-governance, .gemini/skills/portfolio-governance, .github/skills/portfolio-governance and .opencode/skills/portfolio-governance in your project.
What does Portfolio Governance need to run?
SKILL.md names no scripts, command-line tools or credentials: Portfolio Governance is instructions for the agent only.
Does Portfolio Governance 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 Portfolio Governance 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 Portfolio Governance use?
Portfolio Governance 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 Portfolio Governance use?
About 935 tokens (SKILL.md is roughly 3.7k 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 461 tokens, read only when the agent opens those files.
What are the alternatives to Portfolio Governance?
Skills that share tags, products or a category with Portfolio Governance: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Portfolio Governance?
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.