process-design skillA
process-design is agent-read markdown (skill) from cbrock84/headcount: Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process..
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
# Process design ## Map what happens, not what is supposed to happen Follow a real instance end to end and record every step, handoff, wait, and rework loop. Talk to the people doing it, who will describe several steps that exist nowhere in the documentation and one or two that everyone has quietly stopped doing. Then measure two things: - **Touch time** — how long the work actually takes. - **Elapsed time** — how long it takes to get through. The gap between them is the process. In most broken processes, work is waiting more than ninety percent of the time, which means speeding up the work changes almost nothing. Attack the waits. ## Find the real constraint One step governs throughput. Improving anything else produces inventory in front of the constraint and no more output. Find it: the step with a queue in front of it. Common constraints that are not the obvious step: a single approver, a specialist everything routes through, a system that only one team can access, and a batch cycle that makes everything wait for the weekly run. ## Redesign In this order, because the order is the leverage: …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/process-design@git:20260916.e72e404mdr add cbrock84/headcount/process-design@sha256:e7e9e1d5d5127e25Pin 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_ra6g7jcst6pjjb52)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,335 B | A | view · diff |
| git:20260901.aa45383 | 2026-09-01 | aa45383 | 2,996 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 2,675 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 (3335 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_ra6g7jcst6pjjb52 GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/process-design GET https://markdownregistry.com/api/v1/blob/e7e9e1d5d5127e25da7a0a7f260935b14169ee2a0a049e612c6208febf183a7a
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.