mcpField
R
rhdh-jira-sprint-plan

rhdh-jira-sprint-plan

github.com/redhat-developerProductivity1954 installsUpdated 1d ago
Repository

About rhdh-jira-sprint-plan

rhdh-jira-sprint-plan prepares figures for RHDH sprint planning by analyzing the upcoming sprint. It is for teams preparing a planning call; it reports capacity and velocity without making changes or assigning work without approval.

Key features

  1. 01Upcoming sprint planning figures
  2. 02Velocity averaged across three named sprints
  3. 03Issue-by-issue carryover accounting
  4. 04Capacity calculation with subtraction shown
  5. 05Fill suggestions without automatic assignment

Use cases

  1. 01Prepare figures before a bi-weekly planning call
  2. 02Review carryover and available sprint capacity
  3. 03Assess whether story-point coverage supports a velocity estimate

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-jira-sprint-plan

After installing, type/rhdh-jira-sprint-planin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlworkflows/plan-sprint.md

Details

From the project README

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.
  • Pre-refinement ceremony analysis and facilitator brief is /rhdh-prepare-refinement.
  • 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.
  • Whether a team can fit rhdh-X.Y-candidate Features through Code Freeze is /rhdh-release-capacity-plan. This skill fills the next sprint only.
  • 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.

Comments

Markdown supported