jira-sprint-summary
starsforks
How to install jira-sprint-summary?
opendatahub-io/ai-helpers/jira-sprint-summary
$npx -y skills add opendatahub-io/ai-helpers --skill jira-sprint-summaryGenerate comprehensive sprint summaries by analyzing JIRA sprint data, including issue breakdown, progress metrics, and team performance insights.
SKILL.md
| 1 | ## Name |
| 2 | odh-ai-helpers:jira-sprint-summary |
| 3 | |
| 4 | ## Synopsis |
| 5 | ``` |
| 6 | /jira:sprint-summary <sprint-name> [options] |
| 7 | ``` |
| 8 | |
| 9 | ## Description |
| 10 | 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. |
| 11 | |
| 12 | ## Parameters |
| 13 | - `sprint-name`: The exact name or identifier of the sprint (required) |
| 14 | - `[options]`: Optional flags for customizing output (see Options section) |
| 15 | |
| 16 | ## Prerequisites |
| 17 | - JIRA MCP server must be configured and accessible |
| 18 | - Appropriate JIRA permissions to access sprint and issue data |
| 19 | - Valid sprint name that exists in the configured JIRA instance |
| 20 | |
| 21 | ## Implementation |
| 22 | |
| 23 | ### Core Features |
| 24 | 1. **Sprint Overview**: Retrieve basic sprint information (dates, status, goals) |
| 25 | 2. **Issue Analysis**: Categorize and analyze all issues in the sprint by: |
| 26 | - Issue type (Story, Bug, Task, Epic, etc.) |
| 27 | - Status (To Do, In Progress, Done, etc.) |
| 28 | - Priority levels |
| 29 | - Assignee distribution |
| 30 | 3. **Progress Metrics**: Calculate completion rates, velocity, and burndown data |
| 31 | 4. **Team Insights**: Analyze workload distribution and individual contributions |
| 32 | 5. **Quality Metrics**: Identify blocked issues, overdue items, and technical debt |
| 33 | |
| 34 | ### Error Handling |
| 35 | - **Missing JIRA Configuration**: If JIRA MCP server is not configured or not working, provide clear setup instructions and troubleshooting steps |
| 36 | - **Missing Sprint Name**: If no sprint name provided, prompt for required parameter with examples |
| 37 | - **Invalid Sprint**: If sprint doesn't exist, suggest similar sprint names or provide guidance on finding correct sprint identifiers |
| 38 | - **Permission Issues**: Log authentication and authorization errors, report the failure to the user, and provide actionable feedback |
| 39 | |
| 40 | ### Output Format |
| 41 | Generate a structured markdown report including: |
| 42 | - Executive summary with key metrics |
| 43 | - Sprint overview (dates, goals, team members) |
| 44 | - Issue breakdown tables and charts |
| 45 | - Progress visualization (completion rates, velocity trends) |
| 46 | - Risk assessment (blocked items, potential delays) |
| 47 | - Recommendations for sprint improvement |
| 48 | |
| 49 | ## Options |
| 50 | - `--format`: Output format (markdown, json, csv) - default: markdown |
| 51 | - `--include-subtasks`: Include subtasks in analysis - default: false |
| 52 | - `--detailed`: Generate detailed issue-by-issue breakdown - default: false |
| 53 | - `--export`: Save summary to file with timestamp - default: false |
| 54 | |
| 55 | ## Usage Scenarios |
| 56 | - **Sprint Retrospectives**: Generate data-driven insights for team retrospective meetings |
| 57 | - **Stakeholder Reporting**: Create executive summaries for leadership updates |
| 58 | - **Performance Tracking**: Monitor team velocity and delivery consistency over time |
| 59 | - **Process Improvement**: Identify bottlenecks and areas for workflow optimization |
| 60 | - **Planning Sessions**: Use historical data to inform future sprint planning |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
