severity-vs-priority-reference SKILL.md skillA
severity-vs-priority-reference from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/severity-vs-priority-reference@git:20260813.bc28491Pins git:20260813.bc28491 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-defect-management/skills/severity-vs-priority-reference/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260813.bc28491, committed Aug 13, 2026
- First version recorded
- Jul 6, 2026
- Size
- 12,182 bytes
- Repository stars
- 11
- License
- MIT
Pure-reference catalog for defect classification: severity (impact on the system / user) vs priority (urgency of fix) on independent axes - the canonical 5-point severity scale (Critical / High / Medium / Low / Trivial), the 5-point priority scale (Immediate / High / Medium / Low / Deferred), the 5x5 matrix with worked S1/P5 and S5/P1 examples, and IEEE 1044-2009 severity classes; plus the full defect lifecycle (ISTQB-canonical states new / open / assigned / fixed / verified / closed /…
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
# severity-vs-priority-reference ## Overview Severity and priority are **two independent axes**, not synonyms. Every triaged defect must have both, and the combination drives scheduling, escalation, and SLA enforcement. - **Severity** measures how badly the defect breaks the system / user when triggered. It's an objective property of the defect. - **Priority** measures how urgently the fix must land. It's a scheduling decision, influenced by severity but also by business context (customer commitments, regulatory deadlines, release timing). This skill is a **pure reference** consumed by defect-report review (which rejects reports that conflate the two), `bug-tracker-workflow`, and downstream triage tooling. Two companion references extend it: the defect **lifecycle** (states, allowed / forbidden transitions, tracker vocabulary) in [references/lifecycle.md](references/lifecycle.md), and the **categorisation taxonomies** (IEEE 1044, ISTQB CTAL-TA root cause, ODC) in [references/taxonomy.md](references/taxonomy.md). ## When to use - Reviewing whether a bug report's severity + priority are both set and consistent with the defect description. …
Read the whole file at its exact version.
How to install
mdr add testland/qa/severity-vs-priority-reference@sha256:6df7c49c74694cb1The line at the top of this page pins the label git:20260813.bc28491, 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_b2gacriflcvo6b5y)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 6, 2026 and Aug 13, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260813.bc28491 latest | 2026-08-13 | bc28491 | 12,182 B | A | view · diff |
| git:20260726.19ddd36 | 2026-07-26 | 19ddd36 | 11,285 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 9,650 B | A | view · diff |
| git:20260718.ab29907 | 2026-07-18 | ab29907 | 9,889 B | A | view · diff |
| git:20260706.4e1409c | 2026-07-06 | 4e1409c | 10,000 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 (12182 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
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b2gacriflcvo6b5y GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/severity-vs-priority-reference GET https://markdownregistry.com/api/v1/blob/6df7c49c74694cb1aea60b4e266cf8b171d46c8b652cb31c8b176f8ed31893d0
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.