How do I install the Rhdh Jira Sprint Plan skill?

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

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 Plan 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 Plan?

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

Rhdh Jira Sprint Plan by redhat-developer

Name: Rhdh Jira Sprint Plan
Author: redhat-developer

Rhdh Jira Sprint Plan

Builds the planning package for an RHDH scrum team's next sprint from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: carryover from the active sprint, three-sprint velocity, per-member capacity, the ready-for-planning queue, available capacity, suggested fill, critical customer bugs, and retro action items. Use for "plan the sprint", "sprint planning prep", "what's our capacity next sprint", "what can we commit to", or "what's carrying over". Works on a team and a sprint, not on one issue — a bare key such as RHIDP-1234 is not a sprint. Looks forward at the sprint that has not started; summarizing the one that just ended is a different job.

redhat-developer ed9342f 3 files · 8.4 KB Updated Sep 17, 2026

File contents

Plan an RHDH sprint

Produce the numbers a planning call needs, before the call. Read-only until the team decides something.

Route

Load workflows/plan-sprint.md. Run it before each bi-weekly sprint planning call.

Boundary with the neighbouring skills

The review of the sprint that just ended — committed versus completed, per-member results, demo checklist — is /rhdh-jira-sprint-report. This skill looks forward; that one looks back.
Making the backlog worth planning from is /rhdh-jira-refine.
Picking and setting an assignee is /rhdh-jira-update. This skill invokes it for fill suggestions rather than scoring assignees itself.
Board IDs, sprint naming, JQL, and the Team field's JQL limitation are /rhdh-jira-api.
Release-level readiness is /rhdh-release-status.

Completion

Complete when velocity names the three sprints it averaged, carryover names every issue counted, and available capacity shows the subtraction that produced it. Report the JQL behind each number and whether any search was truncated. Say when story-point coverage is too thin to trust a velocity figure rather than publishing a number that looks solid. Fill suggestions are presented as suggestions — team members self-select during planning, and nothing here assigns anyone without approval.

---name: rhdh-jira-sprint-plandescription: Builds the planning package for an RHDH scrum team's next sprint from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: carryover from the active sprint, three-sprint velocity, per-member capacity, the ready-for-planning queue, available capacity, suggested fill, critical customer bugs, and retro action items. Use for "plan the sprint", "sprint planning prep", "what's our capacity next sprint", "what can we commit to", or "what's carrying over". Works on a team and a sprint, not on one issue — a bare key such as RHIDP-1234 is not a sprint. Looks forward at the sprint that has not started; summarizing the one that just ended is a different job.---# Plan an RHDH sprintProduce the numbers a planning call needs, before the call. Read-only until theteam decides something.## RouteLoad `workflows/plan-sprint.md`. Run it before each bi-weekly sprint planningcall.## Boundary with the neighbouring skills- The review of the sprint that just ended — committed versus completed, per-member results, demo checklist — is `/rhdh-jira-sprint-report`. This skill looks forward; that one looks back.- Making the backlog worth planning from is `/rhdh-jira-refine`.- Picking and setting an assignee is `/rhdh-jira-update`. This skill invokes it for fill suggestions rather than scoring assignees itself.- Board IDs, sprint naming, JQL, and the Team field's JQL limitation are `/rhdh-jira-api`.- Release-level readiness is `/rhdh-release-status`.## CompletionComplete when velocity names the three sprints it averaged, carryover names everyissue counted, and available capacity shows the subtraction that produced it.Report the JQL behind each number and whether any search was truncated. Say whenstory-point coverage is too thin to trust a velocity figure rather thanpublishing a number that looks solid. Fill suggestions are presented assuggestions — team members self-select during planning, and nothing here assignsanyone without approval.

Frequently asked questions