How do I install the Rhdh Jira Sprint Report skill?

Run npx skillmds@latest add redhat-developer/rhdh-jira-sprint-report 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 Sprint Report 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 Sprint Report?

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 Sprint Report free to use?

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

Who published Rhdh Jira Sprint Report?

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

Rhdh Jira Sprint Report by redhat-developer

Name: Rhdh Jira Sprint Report
Author: redhat-developer

Rhdh Jira Sprint Report

Summarizes an RHDH sprint that has finished or is finishing, from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: committed versus completed story points, scope added mid-sprint, per-member breakdown, epic progress, the demo checklist with RHDH file and slide naming, and the velocity trend. Use for "sprint report", "what did we complete this sprint", "sprint review prep", "how did the sprint go", or "which demos do we owe". Looks back at work already done; preparing the sprint that has not started yet is a different job, and a single issue such as RHIDP-1234 is not a sprint.

redhat-developer 045decc 3 files · 7.4 KB Updated Sep 17, 2026

File contents

Report on an RHDH sprint

Say what the sprint actually delivered, with the numbers traceable to a query. Read-only.

Route

Load workflows/summarize-sprint.md. Run it at the end of a sprint, before the review and demo meeting.

Boundary with the neighbouring skills

Preparing the sprint that has not started — carryover, capacity, ready queue — is /rhdh-jira-sprint-plan. This skill looks back; that one looks forward.
Judging whether individual issues are in good shape is /rhdh-jira-refine.
Board IDs, sprint naming, JQL, and custom field IDs are /rhdh-jira-api.
Release-level readiness across sprints is /rhdh-release-status.

Completion

Complete when committed and completed totals name the sprint and the JQL behind them, the partition into completed, carried over, and added mid-sprint accounts for every issue in the sprint, and epic progress states both the numerator and the denominator. Report whether any search was truncated. The per-member breakdown says out loud that it covers only Jira-tracked work — code review, documentation, support, and meetings do not appear in it, and someone with zero completions has not necessarily done nothing.

Frequently asked questions