skills.rest
ericfisherdev
ericfisherdevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

backlog-summary

Fetches token-efficient Jira issue summaries with sprint-aware caching and scope filters.

1|Updated Dec 9, 2025
Search Tags:#reporting#backlog#issues#jira#summary#sprint
One-click install
npx skills add https://github.com/ericfisherdev/claude-plugins --skill backlog-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backlog-summary
Source: https://github.com/ericfisherdev/claude-plugins/tree/main/plugins/jira-tools/skills/backlog-summary
Command: npx skills add https://github.com/ericfisherdev/claude-plugins --skill backlog-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira_cache, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a quick, token-efficient summary of Jira issues, helping users understand project status without sifting through excessive detail.

Core Features & Use Cases

  • Bulk Issue Listing: Get an overview of issues in a project, backlog, or sprint.
  • Token Efficiency: Optimized for minimal token usage by fetching only essential fields (key, status, labels, summary).
  • Use Case: A project manager needs to quickly see all open bugs in the current sprint to assess progress.

Quick Start

Use the backlog-summary skill to get a summary of all issues in the EFT project.

Frequently Asked Questions about backlog-summary

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

FAQPage Schema
How do I get a summary of Jira issues in a sprint without using too many tokens?▼

You can fetch a token-efficient summary of Jira issues by retrieving only essential fields like key, status, labels, and summary. This approach minimizes token usage while providing a clear overview of sprint progress.

Can I filter Jira backlog issues by labels and statuses?▼

Yes, Jira backlog issues can be filtered by labels and statuses. The skill supports filtering by scope such as backlog, active-sprint, and past-sprints, along with discovery commands to list available statuses and labels.

What is the best way to summarize Jira issues for a quick project status check?▼

The best way to summarize Jira issues for a quick status check is using sprint-aware caching that reduces API calls. Fetching compact, JSON, or text output formats provides a fast overview without sifting through excessive detail.

Does the Jira issue summary skill require any specific dependencies to work?▼

Yes, the Jira issue summary skill requires the jira_cache dependency to function. This shared caching mechanism enables sprint-aware caching, which reduces redundant API calls during issue retrieval.

How do I list all Jira issues in an active sprint using compact output?▼

You can list all Jira issues in an active sprint by filtering with the active-sprint scope and selecting the compact output format. This retrieves only essential fields, ensuring minimal token consumption.

Related Skills

Explore More Software Engineering Skills→
njohnson101njohnson101

ib-insync

Connect to Interactive Brokers TWS/Gateway API and place orders with ib_insync.

Community
Advanced
ericfisherdevericfisherdev
1

sprint-report

Generate sprint reports with progress, issue breakdowns, and velocity metrics from Jira.

Community
Intermediate
FrekiManagarmFrekiManagarm

github-project-management

Automate GitHub issue triage, decomposition, and project board synchronization.

Community
Intermediate
markus41markus41
18

jira:status

Retrieve the status of a current Jira work session or issue.

Community
Basic