org-design skillA
org-design is agent-read markdown (skill) from cbrock84/headcount: Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons..
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
# Org design Structure determines what is easy and what requires heroics. Most persistent coordination problems are structural and cannot be fixed by asking people to communicate better. ## Design from the work Start with the work that must happen and its natural boundaries — where handoffs are expensive, and where they are cheap. Draw team lines at the cheap handoffs. Then check: can each team deliver something meaningful without waiting on another? A team that cannot ship without three dependencies is not a team, it is a queue. **Design the org for the work, not around the people currently in it.** Then reconcile deliberately, noting where you have compromised and why. Structures built around individuals fail when those individuals leave, and everyone can see they were built that way. ## Spans and layers Wide spans push decisions down and starve people of attention. Narrow spans give attention and breed layers, which add latency to every decision. Roughly: five to nine reports for a manager whose people need coaching; more where the work is consistent and the people are experienced. Every layer must add decision value — a layer that only …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/org-design@git:20260916.e72e404mdr add cbrock84/headcount/org-design@sha256:fe43beb4332dc0abPin 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_36qg4oc2ccgpgbw4)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,320 B | A | view · diff |
| git:20260828.f80dcb5 | 2026-08-28 | f80dcb5 | 2,981 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 (3320 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_36qg4oc2ccgpgbw4 GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/org-design GET https://markdownregistry.com/api/v1/blob/fe43beb4332dc0ab8bd9fd59c120686c8d40c2589aa9accecb142913ec14153b
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.
More from cbrock84/headcount
Every file in cbrock84/headcount