work-items-to-jira SKILL.md skillA
work-items-to-jira from testdouble/han is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testdouble/han/work-items-to-jira@git:20260818.55bdb1dPins git:20260818.55bdb1d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testdouble/han
- Path
han-atlassian/skills/work-items-to-jira/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260818.55bdb1d, committed Aug 18, 2026
- First version recorded
- Jul 30, 2026
- Size
- 17,228 bytes
- Repository stars
- 338
- License
- MIT
Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not post to GitHub — use…
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
## Project Context
- personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"`
- project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""`
As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read
that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md`
probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
# Work Items to Jira Tickets
Take an already-broken-down `work-items.md` file (produced by `/plan-work-items`) and publish each slice as a Jira
ticket in a single target project.
The breakdown work — drafting slices, assigning symbolic IDs, specifying dependencies, inventorying references — has
already been done upstream. This skill's job is to validate the format, confirm the target, create one ticket per slice
…Read the whole file at its exact version.
How to install
mdr add testdouble/han/work-items-to-jira@sha256:1dc14bc456396737The line at the top of this page pins the label git:20260818.55bdb1d, 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_e5jgwedzr2b4h7ay)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 30, 2026 and Aug 18, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260818.55bdb1d latest | 2026-08-18 | 55bdb1d | 17,228 B | A | view · diff |
| git:20260731.e79299f | 2026-07-31 | e79299f | 17,116 B | A | view · diff |
| git:20260731.e50fe27 | 2026-07-31 | e50fe27 | 17,321 B | A | view · diff |
| git:20260730.78dc4f8 | 2026-07-30 | 78dc4f8 | 17,329 B | A | view · diff |
| git:20260730.e86a73d | 2026-07-30 | e86a73d | 17,149 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 (17228 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
testdouble/han · 338 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e5jgwedzr2b4h7ay GET https://markdownregistry.com/api/v1/resolve?ref=testdouble/han/work-items-to-jira GET https://markdownregistry.com/api/v1/blob/1dc14bc456396737b9bf1b967c836e245d941727dc80c9cc2fa6132dc551aa09
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.