schedule-development-and-analysis skillA
schedule-development-and-analysis is agent-read markdown (skill) from cbrock84/headcount: Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything..
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
# Schedule development and analysis A schedule is a model of how work connects. Most schedules in circulation are a list of dates someone typed, which looks the same in a status deck and behaves completely differently when anything moves. ## Build it from logic, not from dates Every task except the first and last should be connected to something. A task with a date and no predecessor is an assertion; a task with a predecessor is a plan, because when the predecessor moves the task moves with it and the schedule tells you so. - **Finish-to-start** is the default and covers most real dependencies. - **Start-to-start and finish-to-finish** describe overlapping work honestly and are worth using rather than faking the overlap with an earlier date. - **Lags** should represent something real — curing time, a notice period, a review window. A lag used to make dates line up is a hidden assumption. **Hard-coded date constraints are where schedules go to die.** Each one severs the logic at that point, so slippage upstream stops propagating and the schedule keeps reporting a date it can no longer support. ## Float is the information, and the critical path is the consequence …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/schedule-development-and-analysis@git:20260916.e72e404mdr add cbrock84/headcount/schedule-development-and-analysis@sha256:d13e915bd78da16fPin 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_i46agi7uvxwnhwec)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 5,020 B | A | view · diff |
| git:20260901.2cd102d | 2026-09-01 | 2cd102d | 4,681 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 (5020 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_i46agi7uvxwnhwec GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/schedule-development-and-analysis GET https://markdownregistry.com/api/v1/blob/d13e915bd78da16fc877b4934ee11ae115618836e8eb66b866f710ff16a4c612
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.