ticket-lifecycle SKILL.md skillA
ticket-lifecycle from prabhdeepsingh/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prabhdeepsingh/claude-plugins/ticket-lifecycle@git:20260826.0b4d903Pins git:20260826.0b4d903 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prabhdeepsingh/claude-plugins
- Path
sonu/skills/ticket-lifecycle/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260826.0b4d903, committed Aug 26, 2026
- First version recorded
- Aug 1, 2026
- Size
- 27,799 bytes
- Repository stars
- 4
- License
- MIT
The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding whether a trigger may move. Never a workflow itself — [[ticket-triage]] specs, [[classify-tickets]] grooms, [[bug-finder]] files; they consult this rulebook.
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
# Ticket lifecycle — the tracker is the control plane A queue-driven flow only works when humans and agents coordinate somewhere durable, and that somewhere is the issue tracker. A ticket records the problem, the scope, the acceptance criteria, the decisions, and the evidence; a tiny set of markers records who authorized what. This skill is the one home for those rules, so the three ticket workflows, the dispatcher, and five tracker backends cannot drift apart on what a claim means or what a priority is worth. Two ideas carry the whole design. **The ticket is the spec** — everything downstream inherits its precision. And **the human is the trigger** — there is no daemon polling anything, so every pass is authorized by a person and gated by a person. ## How to apply this Load this before touching any ticket. Then, in order: resolve the tracker (section 1), read the resolved adapter for the mechanics (section 2), and run your workflow's own pass under the rules in sections 3 through 9. A workflow never names tracker mechanics itself — it names an *operation* and lets the resolved adapter supply the command. --- ## 1. Resolve the tracker before anything else …
Read the whole file at its exact version.
How to install
mdr add prabhdeepsingh/claude-plugins/ticket-lifecycle@sha256:54b06c5682d9f23fThe line at the top of this page pins the label git:20260826.0b4d903, 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_idfdvkcrcebdjioq)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 1, 2026 and Aug 26, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260826.0b4d903 latest | 2026-08-26 | 0b4d903 | 27,799 B | A | view · diff |
| git:20260825.06c64c5 | 2026-08-25 | 06c64c5 | 28,467 B | A | view · diff |
| git:20260801.179ef1c | 2026-08-01 | 179ef1c | 27,897 B | A | view · diff |
| git:20260801.ca5fe0c | 2026-08-01 | ca5fe0c | 21,868 B | A | view · diff |
| git:20260801.94f8ff0 | 2026-08-01 | 94f8ff0 | 19,669 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 (27799 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
prabhdeepsingh/claude-plugins · 4 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_idfdvkcrcebdjioq GET https://markdownregistry.com/api/v1/resolve?ref=prabhdeepsingh/claude-plugins/ticket-lifecycle GET https://markdownregistry.com/api/v1/blob/54b06c5682d9f23fbf9022e7f84f220c8f9c426c0c6570054cda34b4f4ca76be
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.