mcpField
R
rhdh-jira-sprint-report

rhdh-jira-sprint-report

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

About rhdh-jira-sprint-report

A read-only skill for reporting what an RHDH sprint delivered, with totals traceable to Jira queries. It accounts for issue outcomes and epic progress, and clarifies the limits of per-member Jira data.

Key features

  1. 01Committed and completed totals
  2. 02Issue outcome breakdown
  3. 03Epic progress numerator and denominator
  4. 04Search truncation reporting
  5. 05Jira-tracked work caveat

Use cases

  1. 01Prepare a sprint review and demo report
  2. 02Compare committed work with completed work
  3. 03Show carryover and mid-sprint additions
  4. 04Report epic progress with traceable counts

Install

Copy the command and run it in a terminal.

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

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

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

Details

From the project README

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.
  • Whether a team can fit rhdh-X.Y-candidate Features through Code Freeze is /rhdh-release-capacity-plan.
  • 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.

Comments

Markdown supported