prioritization skillA
prioritization is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Choose what not to do and make the tradeoff legible — the constraint being spent, each candidate's cost and value with the evidence behind it, what is reversible, and what would change the answer. Use when a list is longer than the capacity, when asked what to cut or what ships first, or when a decision was made and nobody can reconstruct why. Not for deciding whether a problem is real (product-discovery), not for writing the scope of what wins (prd-and-stories), and not for committing the team .
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
# Prioritization Ranking is easy and useless. The decision that matters is what gets dropped, and the artifact that matters is a reason someone can disagree with in three months. ## When this fires More candidates than capacity; a request to say what ships first or what to cut; an existing priority order nobody can justify. It does not fire for a list of two items with an obvious dependency between them — say the order in one line and move on. ## Procedure 1. **Name the constraint you are allocating.** One release, one sprint, one person for two weeks, one review slot. Priority without a stated capacity is just an opinion about importance, and it is why ranked lists get agreed and then ignored. 2. **Make the list comparable.** Candidates at wildly different sizes cannot be ranked against each other. Split the boulders into the first shippable slice, and say explicitly that what is being compared is the slice, not the ambition behind it. 3. **Write the cost honestly, in the unit of the constraint.** Your estimate, its basis, and its uncertainty as a range where you have one. Include the costs that hide outside the build: …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/prioritization@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/prioritization@sha256:86fe440497fa4867Pin 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_s5gcez2tvnkw4oe5)
1 badge views in 30 days
Versions
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 (6169 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s5gcez2tvnkw4oe5 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/prioritization GET https://markdownregistry.com/api/v1/blob/86fe440497fa486740f1b90e6c3b488393e1a28100de7efbe069636db9a7d022
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 nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher