portfolio-governance skillA
portfolio-governance is agent-read markdown (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..
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
# 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 …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/portfolio-governance@git:20260916.e72e404mdr add cbrock84/headcount/portfolio-governance@sha256:e48d6ff022343949Pin 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_lkyizrloiyxkscd3)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,754 B | A | view · diff |
| git:20260829.2464776 | 2026-08-29 | 2464776 | 3,415 B | A | view · diff |
| git:20260829.3b7c308 | 2026-08-29 | 3b7c308 | 3,415 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 (3754 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_lkyizrloiyxkscd3 GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/portfolio-governance GET https://markdownregistry.com/api/v1/blob/e48d6ff0223439493377f6a245496aa25a7f459e912d1b99f38d77626d3ace37
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.