skills.rest
mulhamna
mulhamnaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sprint-summary

Summarize Jira sprint issues grouped by status and assignee.

46|12|Updated Apr 15, 2026
Search Tags:#command line#jira#agile planning#status reporting#sprint summary#project key#assignee breakdown
One-click install
npx skills add https://github.com/mulhamna/jira-commands --skill sprint-summary-mulhamna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-summary
Source: https://github.com/mulhamna/jira-commands/tree/main/plugin/skills/sprint-summary
Command: npx skills add https://github.com/mulhamna/jira-commands --skill sprint-summary-mulhamna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of quickly understanding how a Jira sprint is progressing—by status totals and who’s assigned—without manually scanning tickets.

Core Features & Use Cases

  • Summarizes sprint outcomes: Produces a compact overview of issues grouped by status and assignee.
  • Supports current or named sprints: Lets you summarize the open/current sprint or a specific sprint you specify.
  • Works as a fast operational check: Useful for standups, planning updates, and sprint health/status reporting for teams using Jira.

Quick Start

Ask for a sprint overview by running the sprint summary for your Jira project key (and optionally the sprint name) so you receive totals and grouped issue details.

Frequently Asked Questions about sprint-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a Jira sprint summary without manually scanning tickets?▼

A Jira sprint summary replaces manual ticket scanning by grouping issues by status and assignee to provide clear totals. You simply specify your project key and optionally a sprint name to receive a compact operational overview.

Can I summarize a specific past Jira sprint instead of the current one?▼

You can summarize a specific named Jira sprint by providing the sprint name along with your project key. If you omit the sprint name, the summary defaults to summarizing the current open sprint.

What's the best way to generate a status report for Jira agile planning?▼

Generating a Jira sprint status report is done by running the issue sprint-summary command via the jirac CLI. It outputs grouped issue totals by assignee and status, serving as a fast operational check for standups.

Do I need the jirac CLI to view assignee breakdowns for my Jira project?▼

Yes, the jirac CLI is required to execute the sprint-summary command and retrieve the assignee breakdown. This command-line tool queries your Jira project key to produce the grouped status totals.

How does sprint summary grouping work for Jira status reporting?▼

Sprint summary grouping works by querying a Jira project key and aggregating issues into clear grouped totals by status and assignee. This provides an at-a-glance update for either the current open sprint or a named sprint.

Related Skills

Explore More Product & Management Skills→
mulhamnamulhamna
46

Change a Jira issue to another issue type using Jira's native move semantics with jirac

Change a Jira issue type while preserving its key using jirac CLI.

Community
Intermediate
shogo-labsshogo-labs
12

standup-collect

Collect daily standup updates and compile summaries from chat channels.

Official
Intermediate
YoshikemoloYoshikemolo
5

devflow-planning

Analyze Jira velocity and capacity to forecast sprint outcomes.

Community
Advanced
ginkidaginkida
20

jira

Manage Jira Cloud or Data Center issues, sprints, workflows, and reports.

Community
Intermediate