track-work SKILL.md skillA
track-work from moonray/repoprompt-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add moonray/repoprompt-workflows/track-work@git:20261014.9babf9cPins git:20261014.9babf9c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- moonray/repoprompt-workflows
- Path
.agents/skills/track-work/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261014.9babf9c, committed Oct 14, 2026
- First version recorded
- Jul 14, 2026
- Size
- 26,505 bytes
- Repository stars
- 11
- License
- MIT
Use FIRST when work is about to start on any repo — a bug is reported, a feature/enhancement is requested, an open question or design decision is raised, someone asks to "track"/"log"/"add a ticket for" something, asks what is open / in-progress / done, or an agent is about to implement a change that has no tracking item. Creates or updates one tracking item in GitHub Issues when origin is GitHub, or a committed file backlog under .agents/issues/ otherwise; temporary GitHub access failures…
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
# Track Work — one live status ledger per repo ## Intent Every bug, feature, enhancement, or decision a repo works on is tracked as **one work item** in **one place**: **GitHub Issues** when the repo has a GitHub remote, else a committed file-based backlog under `.agents/issues/`. That item is the **status** source of truth (draft / backlog / in-progress / review / done). The repo's long-form files — specs, plans, loops, research — stay as the **detail** layer and are *linked* from the item, never duplicated. This is the entry gate: **no implementation, no spec edit, no test starts before the work has a tracking item** (or is confirmed to update an existing one). ## Workspace scope — multi-repo fan-out The ledger is per-repo, but questions often aren't. A workspace-level question — "what's open?", "list open issues by priority", "what should I work on next?" — spans **every repo in the workspace**: in RPCE, every loaded root that is a git repo (plus any repo the question names); elsewhere, every checkout the workspace covers. Answering it from the primary repo alone presents a partial list as complete, which is the one failure this section exists to prevent. …
Read the whole file at its exact version.
How to install
mdr add moonray/repoprompt-workflows/track-work@sha256:cf42515df21e45feThe line at the top of this page pins the label git:20261014.9babf9c, 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_lo3fsyq7zvgxcnm3)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 14, 2026 and Oct 14, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.9babf9c latest | 2026-10-14 | 9babf9c | 26,505 B | A | view · diff |
| git:20261008.d3dbbb2 | 2026-10-08 | d3dbbb2 | 25,030 B | A | view · diff |
| git:20260820.63ac0b2 | 2026-08-20 | 63ac0b2 | 23,818 B | A | view · diff |
| git:20260820.21511c0 | 2026-08-20 | 21511c0 | 22,648 B | A | view · diff |
| git:20260721.5b70859 | 2026-07-21 | 5b70859 | 21,713 B | A | view · diff |
| git:20260714.235fe5b | 2026-07-14 | 235fe5b | 21,723 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 (26505 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
moonray/repoprompt-workflows · 11 stars · license MIT · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lo3fsyq7zvgxcnm3 GET https://markdownregistry.com/api/v1/resolve?ref=moonray/repoprompt-workflows/track-work GET https://markdownregistry.com/api/v1/blob/cf42515df21e45feb7945061b131c864cb854d8c468fcd3825817e8927ad705e
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.
More from moonray/repoprompt-workflows
Every file in moonray/repoprompt-workflows