benefits-realization skillA
benefits-realization is agent-read markdown (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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/benefits-realization@git:20260916.e72e404mdr add cbrock84/headcount/benefits-realization@sha256:f11fefd4a986585ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_pmflsi2g2b4ijsj3)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,463 B | A | view · diff |
| git:20260829.3b7c308 | 2026-08-29 | 3b7c308 | 3,124 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3463 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pmflsi2g2b4ijsj3 GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/benefits-realization GET https://markdownregistry.com/api/v1/blob/f11fefd4a986585e8033e6927c3440b9f81d7487e30de1677d527013d669718f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.