From jira-tools
This skill MUST be used when the user asks to "get backlog", "list backlog issues", "show backlog", "what's in the backlog", "backlog summary", "list Jira issues", "show issues in project", "what issues are pending", "show sprint issues", "active sprint", "past sprints", or needs a quick overview of multiple issues. Use this for bulk issue listing - use jira-issue for single issue details.
npx claudepluginhub ericfisherdev/claude-plugins --plugin jira-toolsThis skill uses the workspace's default tool permissions.
Fetch a token-efficient summary of issues from Jira with sprint-aware caching. Returns only essential fields: issue key, status, labels, and summary.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Fetch a token-efficient summary of issues from Jira with sprint-aware caching. Returns only essential fields: issue key, status, labels, and summary.
Use the Python script at scripts/fetch_backlog.py:
# Get all issues in project (default 50)
python scripts/fetch_backlog.py EFT
# Get only backlog issues (not in any sprint)
python scripts/fetch_backlog.py EFT --scope backlog
# Get active sprint issues
python scripts/fetch_backlog.py EFT --scope active-sprint
# Get issues from past/closed sprints
python scripts/fetch_backlog.py EFT --scope past-sprints
| Scope | Description | Cache TTL |
|---|---|---|
all (default) | All issues | Auto-categorized |
backlog | Issues not in any sprint | 12 hours |
active-sprint | Issues in current sprint | 1 hour |
past-sprints | Issues from closed sprints | 24 hours |
# Backlog Vue issues
python scripts/fetch_backlog.py EFT --scope backlog --label vue
# Active sprint excluding legacy
python scripts/fetch_backlog.py EFT --scope active-sprint --exclude-label legacy
# Past sprint issues that are done
python scripts/fetch_backlog.py EFT --scope past-sprints --status Done
# Only open backlog issues
python scripts/fetch_backlog.py EFT --scope backlog --status Open --status "To Do"
# Active sprint, not done
python scripts/fetch_backlog.py EFT --scope active-sprint --exclude-status Done
Most token-efficient. One line per issue:
EFT-123|Open|vue,frontend|Implement dark mode toggle
EFT-124|In Progress|-|Fix login validation
Format: KEY|status|labels|summary (labels - if none)
python scripts/fetch_backlog.py EFT --format json
Returns compact JSON array for programmatic use.
python scripts/fetch_backlog.py EFT --format text
Multi-line human-readable format.
Issues are cached in three categories with different TTLs:
| Category | TTL | Use Case |
|---|---|---|
active_sprint | 1 hour | Issues change frequently during active sprints |
backlog | 12 hours | Backlog items change less frequently |
past_sprints | 24 hours | Closed sprint issues rarely change |
# View cache status
python shared/jira_cache.py info
# Clear all issue cache
python shared/jira_cache.py clear-issues
# Clear only backlog cache
python shared/jira_cache.py clear-issues --category backlog
# Clear only active sprint cache for project
python shared/jira_cache.py clear-issues -p EFT --category active_sprint
# Move issues to past_sprints when sprint closes
python shared/jira_cache.py close-sprint -p EFT --sprint-id 123
List available filter values:
# List sprints for project
python scripts/fetch_backlog.py EFT --list-sprints
# List statuses for project
python scripts/fetch_backlog.py EFT --list-statuses
# List available labels
python scripts/fetch_backlog.py EFT --list-labels
Requires three environment variables:
JIRA_BASE_URL - e.g., https://yoursite.atlassian.netJIRA_EMAIL - Your Jira account emailJIRA_API_TOKEN - API token from Atlassian account settingsThis skill is optimized for minimal token usage:
For detailed single-issue information, use the jira-issue skill instead.
For complete filter options and JQL examples, see references/options-reference.md.