program-management skillA
program-management is agent-read markdown (skill) from cbrock84/headcount: Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates..
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
# Program management Programs fail at the seams between teams, not inside them. The job is the seams. ## Set up - **One outcome, stated as a business result** with a date. Programs with several equal objectives have none. - **A named accountable owner** — one person, not a committee. The program manager drives; the owner decides. - **Scope written as inclusions and exclusions.** The exclusions do the work; unwritten exclusions return as assumptions. - **Dependencies mapped and agreed by the teams that owe them**, with dates they have actually committed to. A dependency in your plan that the owning team has not agreed to is a wish. ## Sequencing Order by dependency and risk, not by team convenience. Front-load the things that could invalidate the plan — the technical unknown, the vendor decision, the approval that might not come. Discovering in month four that the plan was impossible is the characteristic program failure. Build in slack at integration points, not at the end. End-loaded buffer gets consumed early and silently. ## Status that is worth reading Three things, every time: are we on track for the date, what changed since last time, and what …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/program-management@git:20260916.e72e404mdr add cbrock84/headcount/program-management@sha256:38a1496a9ebc6f86Pin 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_5oe24c7akjfopy6g)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,036 B | A | view · diff |
| git:20260829.3b7c308 | 2026-08-29 | 3b7c308 | 2,697 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 (3036 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_5oe24c7akjfopy6g GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/program-management GET https://markdownregistry.com/api/v1/blob/38a1496a9ebc6f86f26b09c444d92a80e54bbb8904753b10a403843a12f3ceeb
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.