Name
odh-ai-helpers:jira-sprint-summary
Synopsis
/jira:sprint-summary <sprint-name> [options]
Description
Generate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights. This command provides data-driven insights for sprint retrospectives, stakeholder reporting, and process improvement.
Parameters
sprint-name: The exact name or identifier of the sprint (required)[options]: Optional flags for customizing output (see Options section)
Prerequisites
- JIRA MCP server must be configured and accessible
- Appropriate JIRA permissions to access sprint and issue data
- Valid sprint name that exists in the configured JIRA instance
Implementation
Core Features
- Sprint Overview: Retrieve basic sprint information (dates, status, goals)
- Issue Analysis: Categorize and analyze all issues in the sprint by:
- Issue type (Story, Bug, Task, Epic, etc.)
- Status (To Do, In Progress, Done, etc.)
- Priority levels
- Assignee distribution
- Progress Metrics: Calculate completion rates, velocity, and burndown data
- Team Insights: Analyze workload distribution and individual contributions
- Quality Metrics: Identify blocked issues, overdue items, and technical debt
Error Handling
- Missing JIRA Configuration: If JIRA MCP server is not configured or not working, provide clear setup instructions and troubleshooting steps
- Missing Sprint Name: If no sprint name provided, prompt for required parameter with examples
- Invalid Sprint: If sprint doesn't exist, suggest similar sprint names or provide guidance on finding correct sprint identifiers
- Permission Issues: Handle authentication and authorization errors gracefully with actionable feedback
Output Format
Generate a structured markdown report including:
- Executive summary with key metrics
- Sprint overview (dates, goals, team members)
- Issue breakdown tables and charts
- Progress visualization (completion rates, velocity trends)
- Risk assessment (blocked items, potential delays)
- Recommendations for sprint improvement
Options
--format: Output format (markdown, json, csv) - default: markdown--include-subtasks: Include subtasks in analysis - default: false--detailed: Generate detailed issue-by-issue breakdown - default: false--export: Save summary to file with timestamp - default: false
Usage Scenarios
- Sprint Retrospectives: Generate data-driven insights for team retrospective meetings
- Stakeholder Reporting: Create executive summaries for leadership updates
- Performance Tracking: Monitor team velocity and delivery consistency over time
- Process Improvement: Identify bottlenecks and areas for workflow optimization
- Planning Sessions: Use historical data to inform future sprint planning
1---2name: usage-scenarios3description: Generate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights.4---56## Name7odh-ai-helpers:jira-sprint-summary89## Synopsis10```11/jira:sprint-summary <sprint-name> [options]12```1314## Description15Generate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights. This command provides data-driven insights for sprint retrospectives, stakeholder reporting, and process improvement.1617## Parameters18- `sprint-name`: The exact name or identifier of the sprint (required)19- `[options]`: Optional flags for customizing output (see Options section)2021## Prerequisites22- JIRA MCP server must be configured and accessible23- Appropriate JIRA permissions to access sprint and issue data24- Valid sprint name that exists in the configured JIRA instance2526## Implementation2728### Core Features291. **Sprint Overview**: Retrieve basic sprint information (dates, status, goals)302. **Issue Analysis**: Categorize and analyze all issues in the sprint by:31 - Issue type (Story, Bug, Task, Epic, etc.)32 - Status (To Do, In Progress, Done, etc.)33 - Priority levels34 - Assignee distribution353. **Progress Metrics**: Calculate completion rates, velocity, and burndown data364. **Team Insights**: Analyze workload distribution and individual contributions375. **Quality Metrics**: Identify blocked issues, overdue items, and technical debt3839### Error Handling40- **Missing JIRA Configuration**: If JIRA MCP server is not configured or not working, provide clear setup instructions and troubleshooting steps41- **Missing Sprint Name**: If no sprint name provided, prompt for required parameter with examples42- **Invalid Sprint**: If sprint doesn't exist, suggest similar sprint names or provide guidance on finding correct sprint identifiers43- **Permission Issues**: Handle authentication and authorization errors gracefully with actionable feedback4445### Output Format46Generate a structured markdown report including:47- Executive summary with key metrics48- Sprint overview (dates, goals, team members)49- Issue breakdown tables and charts50- Progress visualization (completion rates, velocity trends)51- Risk assessment (blocked items, potential delays)52- Recommendations for sprint improvement5354## Options55- `--format`: Output format (markdown, json, csv) - default: markdown56- `--include-subtasks`: Include subtasks in analysis - default: false57- `--detailed`: Generate detailed issue-by-issue breakdown - default: false58- `--export`: Save summary to file with timestamp - default: false5960## Usage Scenarios61- **Sprint Retrospectives**: Generate data-driven insights for team retrospective meetings62- **Stakeholder Reporting**: Create executive summaries for leadership updates63- **Performance Tracking**: Monitor team velocity and delivery consistency over time64- **Process Improvement**: Identify bottlenecks and areas for workflow optimization65- **Planning Sessions**: Use historical data to inform future sprint planning
tools-only