jira-ticket-readyup SKILL.md skillA
jira-ticket-readyup from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/jira-ticket-readyup@git:20260908.263a106Pins git:20260908.263a106 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/project-mgmt/issue-tracker-toolkit/jira-ticket-readyup/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260908.263a106, committed Sep 8, 2026
- First version recorded
- Apr 27, 2026
- Size
- 15,802 bytes
- Repository stars
- 10
- License
- MIT
Ready up Jira tickets for refinement, including brand-new not-yet-keyed backlog items, by gathering context from linked incidents or interviewing the user when no incident exists, populating a YAML template against the project's 'ready for refinement' standard, validating it against a JSON schema plus gap-detection heuristics for testability and vagueness, and generating a structured markdown document. Use when asked to ready up, prepare for refinement, draft a new backlog ticket, or write up…
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
# jira-ticket-readyup Turn a sparse Jira backlog ticket — or a brand-new item with no key yet — into a fully-structured "ready for refinement" document by gathering incident context (or interviewing the user when no source material answers a required question), applying the standard template, and validating the output against both the schema and gap-detection heuristics. ## When to Use This Skill Use jira-ticket-readyup when: - User asks to "ready up" or "prepare for refinement" one or more Jira tickets - A ticket exists but lacks Context, Conditions of Satisfaction, or Acceptance Criteria - User wants to promote a follow-up ticket (spawned from an incident) into a proper backlog item - User wants to draft a brand-new backlog ticket that has no Jira key yet (set `ticket.new_ticket: true` — see Step 2a) **Do NOT use for:** - Tickets that are already in "Ready for Refinement" status with full descriptions ## What a Good Ticket Looks Like A ticket is "ready for refinement" when it has all four sections: | Section | Purpose | |---|---| | **Context** | Background on the service, current behaviour, and why it matters | …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/jira-ticket-readyup@sha256:6fa44620f4689295The line at the top of this page pins the label git:20260908.263a106, 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_iixuwvjvlo63o6ja)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 27, 2026 and Sep 8, 2026, about one every 134 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.263a106 latest | 2026-09-08 | 263a106 | 15,802 B | A | view · diff |
| git:20260427.dfbd28f | 2026-04-27 | dfbd28f | 7,964 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 (15802 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
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iixuwvjvlo63o6ja GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/jira-ticket-readyup GET https://markdownregistry.com/api/v1/blob/6fa44620f4689295f431af7652f3b85fa6c1b933e0b36d3dc8491f3f9a62738d
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.