sprint-review

Generate a Confluence-ready sprint review from Jira issues with story points.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill sprint-review-afoxnyc3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-review
Source: https://github.com/afoxnyc3/chelsea-piers-itops/tree/main/plugins/jira-pm/skills/sprint-review
Command: npx skills add https://github.com/afoxnyc3/chelsea-piers-itops --skill sprint-review-afoxnyc3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It turns Jira sprint issue data into a clear, stakeholder-ready sprint review that highlights what shipped, what carried over, velocity, and the reasons behind delays.

Core Features & Use Cases

  • Sprint outcome analysis: Classifies issues as shipped, carry-over, in-progress, and added mid-sprint.
  • Velocity calculation: Computes completed vs planned story points and can compare against a rolling 3-sprint average when prior data is available.
  • Confluence-ready reporting: Produces a structured report and can optionally publish it to Confluence after collecting the target space and parent page.
  • Blocker identification: Summarizes blocker themes by inspecting comments and linked issues for carry-over items.

Quick Start

Run sprint-review for your target sprint (by sprint ID or project/board key) to generate a Confluence-formatted sprint review report with shipped, carry-over, blockers, risks, and highlights.

Frequently Asked Questions about sprint-review

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

FAQPage Schema
How do I generate a sprint review from Jira issues for stakeholder reporting?

Generate a stakeholder-ready sprint review by analyzing Jira issues from a completed or active sprint, classifying them as shipped, carry-over, in-progress, or mid-sprint additions, and calculating planned vs actual story points velocity.

How do I calculate sprint velocity and compare it against previous sprints in Jira?

Sprint velocity calculation computes completed vs planned story points from Jira issues and can compare against a rolling 3-sprint average when prior sprint data is available from your Atlassian board.

Can I publish a sprint status report directly to Confluence from Jira data?

You can publish a Confluence-ready sprint report by optionally confirming the target space and parent page, which formats the Jira sprint analysis using ADF formatting for direct Confluence publishing.

How do I identify blocker themes for carry-over items in a Jira sprint?

Blocker identification summarizes blocker themes for carry-over items by inspecting Jira issue comments and linked issues, extracting the reasons behind sprint delays for stakeholder visibility.

Do I need an Atlassian MCP server to generate sprint reports from Jira?

Sprint reporting requires an operational Atlassian MCP server named "atlassian" and explicit Jira field selection including story points to analyze sprint issues and produce the review output.

What's the best way to compare planned vs actual delivery for a software sprint?

Comparing planned vs actual delivery analyzes Jira sprint issues to separate shipped items from carry-over and in-progress work, computing story point velocity to highlight delivery gaps for stakeholders.