backlog-routing-by-topic SKILL.md skillA
backlog-routing-by-topic from wei18/apple-dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wei18/apple-dev-skills/backlog-routing-by-topic@git:20260912.64da49aPins git:20260912.64da49a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wei18/apple-dev-skills
- Path
collaboration-skills/skills/backlog-routing-by-topic/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260912.64da49a, committed Sep 12, 2026
- First version recorded
- Jun 24, 2026
- Size
- 3,373 bytes
- Repository stars
- 18
- License
- MIT
Route a stray idea that surfaces mid-task to the §Backlog of the right living doc in a spec-phase-orchestration repo (design.md, foundations.md, plan.md, methodology.md, or today's meeting log) as a single line, without derailing the current work. Use when a not-now-but-don't-forget idea comes up, when tidying a meeting log's parking-lot items, or when asked where an idea should go. Not for decisions that must be acted on now (those belong in the body of plan.md).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Backlog Routing by Topic
## When to invoke
- A "don't handle now but don't forget" idea comes up mid-discussion.
- Tidying a meeting log and re-homing parking-lot items.
- User asks "where does this idea go", "should backlog be split by file".
## Routing rules
| Topic | Destination |
|---|---|
| **Product / gameplay / UX / feature proposal** | `docs/design.md §Backlog` |
| **Tooling / packages / language features / CI / Secrets / L10n** | `docs/foundations.md §Backlog` |
| **Implementation step / refactor / test coverage expansion** | `docs/plan.md §Backlog` |
| **Collaboration mode / agent skill setup / review flow** | `docs/methodology.md §Backlog` |
| **Unclassifiable / highly divergent** | Today's `meetings/{date}_*.md` §Open questions |
| **Mixed (product + tooling)** | File at the bigger decision point; add one cross-ref line in the other |
## Entry format
One line each; if context is needed, attach the meeting log date as a sub-bullet:
```markdown
- Adopt `XcodeSelectiveTesting` to only run impacted test targets in CI (2026-05-15)
- Developers can reproduce GitHub Actions workflows locally via `nektos/act`
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_t7qecjrx7alak3cc/f99a3fed11d9bc70d32fd21cd18f183cebea429acd14093736a83c5887386c05.json
Then /plugin install backlog-routing-by-topic@markdownregistry-t7qecjrx7alak3cc in Claude Code. It installs git:20260912.64da49a, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add wei18/apple-dev-skills/backlog-routing-by-topic@sha256:f99a3fed11d9bc70The line at the top of this page pins the label git:20260912.64da49a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t7qecjrx7alak3cc)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in wei18/apple-dev-skills/backlog-routing-by-topic since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of backlog-routing-by-topic from somewhere else? Ask it: where did my backlog-routing-by-topic come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Jun 24, 2026 and Sep 12, 2026, about one every 27 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.64da49a latest | 2026-09-12 | 64da49a | 3,373 B | A | view · diff |
| git:20260911.e4022a8 | 2026-09-11 | e4022a8 | 3,266 B | A | view · diff |
| git:20260904.bf7ba69 | 2026-09-04 | bf7ba69 | 3,320 B | A | view · diff |
| git:20260624.331609b | 2026-06-24 | 331609b | 3,205 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/backlog-routing-by-topic/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3373 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
wei18/apple-dev-skills · 18 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t7qecjrx7alak3cc GET https://markdownregistry.com/api/v1/resolve?ref=wei18/apple-dev-skills/backlog-routing-by-topic GET https://markdownregistry.com/api/v1/blob/f99a3fed11d9bc70d32fd21cd18f183cebea429acd14093736a83c5887386c05
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.