project-delivery skillA
project-delivery is agent-read markdown (skill) from cbrock84/headcount: Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late..
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
# Project delivery A project is one bounded piece of work with an end. Coordinating several toward a shared outcome is `pmo:program-management`. ## Scope by exclusion Inclusions are agreed easily and understood differently. The exclusions do the work: what this project will *not* deliver, written down and acknowledged by the sponsor. Unwritten exclusions return as assumptions, always late, always framed as something obviously included. Fixing that at the end is called scope creep; it is usually a documentation failure at the start. ## Estimate as a range, and say what the range means A single-point estimate is a forecast presented as a commitment. Give a range with the assumptions that would move it, and be explicit about confidence. Estimate the work, not the desired date. Estimates negotiated downward do not change the work; they change when you find out, and the finding-out happens at the least recoverable moment. Decompose until the pieces are comprehensible. Estimating a large unknown produces a number correlated with optimism rather than with the work. ## The critical path is where attention belongs …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/project-delivery@git:20260916.e72e404mdr add cbrock84/headcount/project-delivery@sha256:671323ee2caefae6Pin 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_x3vx4va6dnvueyjm)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 5,028 B | A | view · diff |
| git:20260901.2cd102d | 2026-09-01 | 2cd102d | 4,689 B | A | view · diff |
| git:20260901.0757404 | 2026-09-01 | 0757404 | 3,461 B | A | view · diff |
| git:20260829.3b7c308 | 2026-08-29 | 3b7c308 | 3,048 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 (5028 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_x3vx4va6dnvueyjm GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/project-delivery GET https://markdownregistry.com/api/v1/blob/671323ee2caefae6f790ba72b48adbd92627292c68951ff3bc153241449307fb
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.