skills.rest
guifry
guifryCOMMUNITY
Explore all skills by this author →
GitHub

jira-debrief

Fetch Jira sprint state, tickets, and blockers for standup preparation.

Updated Jul 6, 2020
Search Tags:#workflow#blockers#jira#sprint#standup#debrief#ticket-status
One-click install
npx skills add https://github.com/guifry/devconfig --skill jira-debrief
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-debrief
Source: https://github.com/guifry/devconfig/tree/main/claude/skills/jira-debrief
Command: npx skills add https://github.com/guifry/devconfig --skill jira-debrief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically surfaces the current Jira sprint state, including assigned tickets and blockers, to streamline standups, sprint reviews, and progress tracking.

Core Features & Use Cases

  • Auto-detects the active sprint and aggregates tickets assigned to you or your team.
  • Identifies blockers and tickets needing review to prioritize during standups.
  • Provides ready-to-use summaries for sprint reviews and status updates.

Quick Start

Ask the AI to run jira-debrief to fetch the current sprint state and generate a standup-ready update.

Frequently Asked Questions about jira-debrief

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

FAQPage Schema
How do I summarize my Jira sprint for a standup?▼

To summarize your Jira sprint for a standup, you need to fetch the active sprint state, assigned tickets, and blockers to generate a structured update. This process aggregates recently updated tickets to streamline progress tracking.

What is the best way to identify Jira blockers for sprint reviews?▼

Identifying Jira blockers for sprint reviews involves auto-detecting the active sprint and filtering tickets needing review or marked as blockers. This surfaces critical impediments to prioritize during team discussions and status updates.

Can I filter Jira sprint tickets by assignee or status?▼

Yes, you can filter Jira sprint tickets by assignee or status to prepare personalized standup updates. This filtering works alongside JQL-based auto-detection to isolate individual or team progress within the active sprint.

How does JQL auto-detection work for sprint state aggregation?▼

JQL auto-detection for sprint state aggregation automatically queries the active Jira sprint using Jira Query Language to retrieve relevant tickets. It then structures the output into tables based on assignee, status, and identified blockers.

Do I need a specific Jira setup to generate standup summaries?▼

You need an active Jira sprint with assigned tickets and logged blockers to generate standup summaries effectively. The process applies to both personal and team contexts where sprint data and recently updated ticket statuses are actively tracked.

Related Skills

Explore More Product & Management Skills→
jpfieldingjpfielding
1

jira-navigator

Query and manage Jira issues, projects, and boards via REST API.

Community
Intermediate
refly-airefly-ai
199

slack

Send custom messages and notifications to specified Slack channels.

Official
Basic
ev3rlitev3rlit

mermaid-kanban

Convert plain-text task lists into Mermaid Kanban diagrams with metadata.

Community
Intermediate
tygwantygwan
1

sync-fix

Detect and fix inconsistencies across Phase tasks, Sprint backlogs, and progress records.

Community
Basic