triage-backlog skillA
This file is byte-identical to the first copy the registry indexed, one of 4 copies on public GitHub. Same content hash, same audit grade.
triage-backlog is agent-read markdown (skill) from phmatray/tagout: Prune and re-decide an EXISTING GitHub issue backlog: verifies which open issues are already fixed or superseded, clusters the rest by root cause, proposes ONE disposition each and executes only what the owner confirms. ALWAYS reach for this when the user wants to prune, triage, groom, re-decide, or take stock of open issues, or says the queue never shrinks: "triage the backlog", "clean up the open issues", "what should we close?", « fais le tri dans les issues », « le backlog ne descend jamais .
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
# Triage the backlog ## What this does `create-issue` opens work, `implement-issue` builds it, `merge-pr` lands it — and `merge-pr` Step 6 opens more, because landing a PR is when deferred work becomes visible. That is a lifecycle with three inlets and no outlet: every issue that ever leaves the queue leaves through a PR, so the queue can only drain at the speed of implementation, while implementation is itself what fills it. This skill is the outlet. It reads the open backlog, works out which items are still real work, which are duplicates of a job already tracked, which were quietly fixed by something else, and which were **observations that got filed as commitments** — then puts a single proposed disposition per item in front of the owner and executes what they confirm. The doctrine comes from `review-followups`, which has always had this outlet for migration reports: closing by decision is *"a legitimate, documented state, never a silent deletion"* — the precedent being *"not pursued by decision, not by lack of capability"*. This skill applies that same idea to GitHub issues, where until now the only documented way out was to build the thing. ## Autonomy contract …
Read the whole file at its exact version.
How to install
mdr add phmatray/tagout/triage-backlog@git:20260914.a9bc0b6mdr add phmatray/tagout/triage-backlog@sha256:aa1dbc66f53c13c7Pin 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_igfcep42qeiyfl54)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.a9bc0b6 latest | 2026-09-14 | a9bc0b6 | 24,159 B | A | view · diff |
| git:20260905.3c46a63 | 2026-09-05 | 3c46a63 | 24,169 B | A | view · diff |
| git:20260905.097cca5 | 2026-09-05 | 097cca5 | 24,126 B | A | view · diff |
| git:20260902.3d3a820 | 2026-09-02 | 3d3a820 | 24,086 B | A | view · diff |
| git:20260831.d1e53de | 2026-08-31 | d1e53de | 24,171 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 (24159 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
phmatray/tagout · 4 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_igfcep42qeiyfl54 GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/tagout/triage-backlog GET https://markdownregistry.com/api/v1/blob/aa1dbc66f53c13c76cc123eba3559b4ae26de6dbef8a1784488b34ecbbe5d797
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.