How do I install the Rhdh Jira Refine skill?

Run npx skillmds@latest add redhat-developer/rhdh-jira-refine in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rhdh Jira Refine safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rhdh Jira Refine?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rhdh Jira Refine free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rhdh Jira Refine?

redhat-developer (@redhat-developer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rhdh Jira Refine by redhat-developer

Name: Rhdh Jira Refine
Author: redhat-developer

Rhdh Jira Refine

Judges whether RHDH Jira work that already exists is ready to move forward — in RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP. Checks an issue, a JQL result, a sprint, or a backlog against the exit criteria for its status, then reports missing fields, hierarchy gaps, likely duplicates, unaddressed comments, stale work, and Feature Exploration readiness. Use for "is RHIDP-1234 ready", "refine this", "refine the backlog", "backlog hygiene", "what's missing on this epic", "run the Feature Exploration checklist", or "which of these are stale". Assesses existing work; it does not open new issues and does not build a sprint.

redhat-developer 1220e0d 3 files · 16.0 KB Updated Sep 17, 2026

File contents

Refine RHDH Jira work

Answer "is this ready" with the criteria the RHDH workflow actually enforces, and say what is missing rather than guessing at it.

Route

Load workflows/refine-issues.md. It covers both the per-issue readiness audit and the Feature Exploration checklist — the same checks, applied at different points in a Feature's life.

Not gated on grilling

Unlike /rhdh-jira-create, this skill does not require the external grilling skill and must not be blocked on it. Refinement reads work that already exists. Gating it on an optional external skill would take a whole capability offline for no benefit.

Reads by default, writes only on request

The report is read-only. When the user asks for fixes, each change becomes an external write: invoke /mutation-gate and follow it. A refine pass typically proposes many small fixes at once, so state them as one set — issue key and exact command per row — rather than approving them one at a time.

Boundary with the neighbouring skills

Opening new work is /rhdh-jira-create.
Updating one known key — status, comment, assignee, link — is /rhdh-jira-update. Refinement reports across many issues; it does not replace that.
Building the next sprint from the refined backlog is /rhdh-jira-sprint-plan.
Exit criteria tables, field IDs, JQL, and the component catalog are /rhdh-jira-api.
Sizing scales, duplicate detection, and decomposition rules are /rhdh-jira-authoring.
What is still open against a release is /rhdh-release-status.

Completion

Complete when every issue the report covers was actually fetched with its custom fields enriched — an unenriched search returns empty Story Points, Team, Size, and Sprint, which looks identical to a field nobody set and is the single most common source of a false "missing data" finding. Report the JQL, the issue count, and whether the result was truncated. Every finding names the check that produced it and its severity. A field that could not be retrieved is reported as unretrieved, never as missing.

---name: rhdh-jira-refinedescription: Judges whether RHDH Jira work that already exists is ready to move forward — in RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP. Checks an issue, a JQL result, a sprint, or a backlog against the exit criteria for its status, then reports missing fields, hierarchy gaps, likely duplicates, unaddressed comments, stale work, and Feature Exploration readiness. Use for "is RHIDP-1234 ready", "refine this", "refine the backlog", "backlog hygiene", "what's missing on this epic", "run the Feature Exploration checklist", or "which of these are stale". Assesses existing work; it does not open new issues and does not build a sprint.---# Refine RHDH Jira workAnswer "is this ready" with the criteria the RHDH workflow actually enforces,and say what is missing rather than guessing at it.## RouteLoad `workflows/refine-issues.md`. It covers both the per-issue readiness auditand the Feature Exploration checklist — the same checks, applied at differentpoints in a Feature's life.## Not gated on grillingUnlike `/rhdh-jira-create`, this skill does **not** require the external`grilling` skill and must not be blocked on it. Refinement reads work thatalready exists. Gating it on an optional external skill would take a wholecapability offline for no benefit.## Reads by default, writes only on requestThe report is read-only. When the user asks for fixes, each change becomes anexternal write: invoke `/mutation-gate` and follow it. A refine passtypically proposes many small fixes at once, so state them as one set — issue keyand exact command per row — rather than approving them one at a time.## Boundary with the neighbouring skills- Opening new work is `/rhdh-jira-create`.- Updating one known key — status, comment, assignee, link — is `/rhdh-jira-update`. Refinement reports across many issues; it does not replace that.- Building the next sprint from the refined backlog is `/rhdh-jira-sprint-plan`.- Exit criteria tables, field IDs, JQL, and the component catalog are `/rhdh-jira-api`.- Sizing scales, duplicate detection, and decomposition rules are `/rhdh-jira-authoring`.- What is still open against a release is `/rhdh-release-status`.## CompletionComplete when every issue the report covers was actually fetched with its customfields enriched — an unenriched search returns empty Story Points, Team, Size,and Sprint, which looks identical to a field nobody set and is the single mostcommon source of a false "missing data" finding. Report the JQL, the issue count,and whether the result was truncated. Every finding names the check that producedit and its severity. A field that could not be retrieved is reported asunretrieved, never as missing.

Frequently asked questions