head-of-pmo skillA
head-of-pmo is agent-read markdown (skill) from cbrock84/headcount: The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it..
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
# Head of the PMO An enterprise PMO exists to make the organization's delivery capacity visible and to force the choices that capacity implies. It does not exist to collect status. ## The two failure modes Every PMO fails in one of two directions, and the remedy for each makes the other worse: - **The reporting PMO.** It aggregates status nobody acts on, and teams learn to write updates that survive review rather than updates that are true. Its meetings are attended and its findings ignored. This is the common one. - **The controlling PMO.** It owns delivery decisions that belong to the teams, becomes a queue everything waits in, and is routed around by anyone with the standing to do so. The line that holds: the PMO owns **which** work proceeds and **whether the organization can absorb it**. Teams own **how** the work gets done. ## What it governs - `pmo:portfolio-governance` — intake, prioritization against real capacity, stage gates that can stop things, and resource contention across projects - `pmo:program-management` and `pmo:project-delivery` — the delivery disciplines themselves …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/head-of-pmo@git:20260916.e72e404mdr add cbrock84/headcount/head-of-pmo@sha256:e913699eb1ff975bPin 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_s7sqikks6gjd74gu)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 5,379 B | A | view · diff |
| git:20260903.cc4a2cd | 2026-09-03 | cc4a2cd | 5,040 B | A | view · diff |
| git:20260901.5eb7d2b | 2026-09-01 | 5eb7d2b | 5,052 B | A | view · diff |
| git:20260831.eaba5fa | 2026-08-31 | eaba5fa | 4,790 B | A | view · diff |
| git:20260829.4a2c133 | 2026-08-29 | 4a2c133 | 3,271 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 (5379 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_s7sqikks6gjd74gu GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/head-of-pmo GET https://markdownregistry.com/api/v1/blob/e913699eb1ff975bac2c33e4a9725abd99e99a38c32a7f31e53754c443b83372
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.