skills.rest
yannmenec
yannmenecCOMMUNITY
Explore all skills by this author →
GitHub

generate-sprint-report

Generate sprint reports with velocity, blockers, scope changes, and recommendations.

2|Updated Mar 10, 2026
Search Tags:#blockers#reporting#velocity#sprint#risk#stakeholders
One-click install
npx skills add https://github.com/yannmenec/delivery-management-skills --skill generate-sprint-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-sprint-report
Source: https://github.com/yannmenec/delivery-management-skills/tree/main/archive/v1/skills/reporting/generate-sprint-report
Command: npx skills add https://github.com/yannmenec/delivery-management-skills --skill generate-sprint-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint teams and stakeholders often struggle to assemble a clear, complete picture of a sprint. This skill generates a comprehensive sprint report by combining velocity, blockers, scope changes, risks, and recommendations from tickets and sprint context, enabling timely, informed decisions.

Core Features & Use Cases

  • Consolidates sprint data (tickets, context, history, and risks) into a single, shareable report.
  • Computes velocity, completion rate, blockers, and scope changes; surfaces trends and risk signals.
  • Produces an executive summary and actionable recommendations with traceable references for stakeholders.

Quick Start

Provide the sprint_tickets, sprint_context, and (optionally) sprint_history to generate the complete sprint report.

Frequently Asked Questions about generate-sprint-report

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

FAQPage Schema
How do I generate a sprint report from Jira tickets for stakeholders?▼

To generate a sprint report, provide your sprint tickets, context, and optionally sprint history. The skill computes velocity, blockers, and scope changes to produce a formatted executive summary with traceable metrics and actionable recommendations.

Can I calculate sprint velocity trends using historical sprint data?▼

Sprint reporting can calculate velocity trends by applying historical sprint data. When you provide sprint history, the report surfaces performance trends alongside current blockers, scope changes, and risk signals to give stakeholders a complete performance picture.

Does sprint reporting require historical data to identify blockers and scope changes?▼

Sprint reporting does not require historical data to identify blockers and scope changes. You only need to provide current sprint tickets and context to compute these metrics, while sprint history is an optional input for calculating velocity trends.

How does sprint reporting handle missing data or incomplete tickets?▼

Sprint reporting flags data gaps when input tickets are incomplete. It ensures all computed metrics are traceable to the provided input data, explicitly highlighting missing information so stakeholders understand the reliability of the generated report.

Related Skills

Explore More Product & Management Skills→
packetalienpacketalien

sprint-status

Summarize sprint health from sprint plan and story statuses.

Community
Intermediate
LucaDeLeoLucaDeLeo
1

bmad-bmm-sprint-status

Summarize sprint progress and surface risks from dashboards and burndown data.

Community
Intermediate
argenargen
1

customer-update

Append customer events to a chronicle entry via script.

Community
Advanced
cnoe-iocnoe-io
392

sprint-progress-report

Generate a structured Markdown sprint progress report from Jira data.

Official
Intermediate