Value Realization
Done-0/value-realization
Judge whether something actually produces value in a concrete scenario.
Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review.
MITAuto-check passed
Install Benefits Realization
$ npx skills add cbrock84/headcount --skill benefits-realization -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount benefits-realization --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/benefits-realization .claude/skills/benefits-realization && 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 "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .claude/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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/benefits-realizationType 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 benefits-realization -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount benefits-realization --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/benefits-realization .agents/skills/benefits-realization && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .agents/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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 benefits-realization -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount benefits-realization --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/benefits-realization .cursor/skills/benefits-realization && 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 "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .cursor/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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/benefits-realization--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 benefits-realization -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount benefits-realization --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/benefits-realization .gemini/skills/benefits-realization && 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 "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .gemini/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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 benefits-realizationInstalls 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 benefits-realization -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/benefits-realization .github/skills/benefits-realization && 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 "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .github/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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 benefits-realization -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 benefits-realization --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/benefits-realization .opencode/skills/benefits-realization && 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 "benefits-realization" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/pmo/skills/benefits-realization into .opencode/skills/benefits-realization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benefits-realization", 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
benefits-realization- GitHub stars
- 2k
- Token cost
- ~861 tokens
- SKILL.md length
- 472 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review.
- SKILL.md covers Define benefits so they can be…, Baseline before you change…, Tracking happens after the… and Post-implementation review…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Benefits Realization is an agent skill from cbrock84/headcount. Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.
Its SKILL.md is about 860 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 benefits-realization skill to ensure projects deliver the value they were approved on — defining measurable benefits, baselining, tracking…”
- “/benefits-realization”
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
Benefits Realization loads about 861 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 472 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). 472 words, ~861 tokens.
Download SKILL.mdSave it as
.claude/skills/benefits-realization/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- benefits-realization
- description
- Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.
Benefits realization
Projects are approved on promised benefits and closed on delivered scope. The gap between those two sentences is why organizations repeat expensive mistakes with confidence.
Define benefits so they can be disproved
A benefit that cannot fail to be claimed is not a benefit. Each needs a measure, a current baseline, a target, a date by which it should appear, and an owner who is accountable after the project closes — usually the operational owner, not the project manager, who has moved on.
Distinguish honestly:
- Cashable — the budget actually reduces. Someone can point at the line.
- Non-cashable — time is released. Real, but only becomes value if that time is redeployed to something that matters, which is a separate management act nobody schedules.
- Cost avoidance — a future cost does not occur. Legitimate and unverifiable, so treat claims sceptically.
- Non-financial — risk reduction, compliance, experience. Often the actual reason. Say so rather than manufacturing a financial number nobody believes.
The most common failure is a business case padded with non-cashable savings presented as though the budget will fall. It will not, and the credibility loss lands on the next case.
Baseline before you change anything
A baseline captured after go-live is not a baseline. Measure first, and record how it was measured — by the time anyone checks, the method will be disputed and nobody will remember.
Tracking happens after the project ends
Benefits appear months after delivery, when the project team has dispersed and attention has moved. This is precisely why it does not happen, and why it needs to be owned by the operational line and scheduled at approval rather than intended.
Set review points at meaningful intervals — ninety days, six months, a year — and hold them regardless of what the answer looks like.
Show full SKILL.md (179 more words)Show less
Post-implementation review worth the hour
Two questions: did the benefits appear, and would we make the same decision knowing what we now know?
Include estimation accuracy, since the systematic bias in an organization's estimates is one of the most useful things it can know about itself and is discoverable only by looking back.
Make it non-punitive or it will produce nothing true. A review that damages careers produces reviews
that say the project was a success. Feed the findings back to
pmo:portfolio-governance and finance:capital-allocation, which are where the next set of
approvals gets made.
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 a case whose benefits have no owner after the project closes.
- Present non-cashable savings as budget reduction.
- Baseline after implementation.
- Run a review that punishes honesty.
© 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/benefits-realization of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Benefits Realization 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 |
|---|---|---|---|---|---|---|
| Benefits Realization this skillcbrock84/headcount | 2k | — | ~861 | Automated safety check: Pass | MIT | |
| Value RealizationDone-0/value-realization | 531 | — | ~11k | Automated safety check: Pass | MIT | |
| Operator Approval Loopaffaan-m/ECC | 276k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Value Propositionphuryn/pm-skills | 27k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Value Prop Statementsphuryn/pm-skills | 27k | — | ~758 | Automated safety check: Pass | MIT | |
| Approvedyoshikawa/rulesync | 1.5k | — | ~429 | Automated safety check: Pass | MIT |
Similar skills
Operator Approval Loop
affaan-m/ECC
Operator approval contract with internal filing notices for agent-drafted outbound messages, hashed drafts, epoch-keyed decisions, durable delivery claims and receipts, and a pre-draft baseline gate.
Value Proposition
phuryn/pm-skills
Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives.
Value Prop Statements
phuryn/pm-skills
Generate value proposition statements for marketing, sales, and onboarding from existing value propositions.
Approve
dyoshikawa/rulesync
Approve a pull request using gh pr review --approve. An agent skill from dyoshikawa/rulesync.
Define Loop
yc-software/qm
Define a Loop — a durable scaffold that works a queue of recurring tasks autonomously (Sentry issues, Front tickets, small perf PRs) with its outputs held for human review.
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.
Questions about Benefits Realization
What does Benefits Realization do?
Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Benefits Realization is an agent skill from cbrock84/headcount. Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review.
How do I install Benefits Realization in Claude Code?
Run `npx skills add cbrock84/headcount --skill benefits-realization -a claude-code`. Or copy the skill folder (plugins/pmo/skills/benefits-realization in cbrock84/headcount) into .claude/skills/benefits-realization in your project. Claude Code loads it when a task matches its description.
How do I install Benefits Realization in Codex?
Run `npx skills add cbrock84/headcount --skill benefits-realization -a codex`. Or copy the skill folder (plugins/pmo/skills/benefits-realization in cbrock84/headcount) into .agents/skills/benefits-realization in your project. Codex loads it when a task matches its description.
Can I use Benefits Realization 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 benefits-realization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/benefits-realization, .gemini/skills/benefits-realization, .github/skills/benefits-realization and .opencode/skills/benefits-realization in your project.
What does Benefits Realization need to run?
SKILL.md names no scripts, command-line tools or credentials: Benefits Realization is instructions for the agent only.
Does Benefits Realization 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 Benefits Realization 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 Benefits Realization use?
Benefits Realization 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 Benefits Realization use?
About 861 tokens (SKILL.md is roughly 3.4k 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 253 tokens, read only when the agent opens those files.
What are the alternatives to Benefits Realization?
Skills that share tags, products or a category with Benefits Realization: Value Realization (Done-0/value-realization, 531 stars), Operator Approval Loop (affaan-m/ECC, 276k stars), Value Proposition (phuryn/pm-skills, 27k stars) and Value Prop Statements (phuryn/pm-skills, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Benefits Realization?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 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.