Run any Skill in Manus with one click

sprint-report

Stars6

Forks3

UpdatedJuly 12, 2026 at 15:23

Analyses Jira sprint data and produces a concise PM-ready report. Use whenever someone shares a sprint report, burndown chart, velocity chart, board screenshot, or Jira ticket data and wants to understand sprint health, delivery confidence, risks, blockers, or team performance. Trigger for phrases like "analyse this sprint", "what does the burndown say", "how is the sprint looking", "write up the sprint report", or "what should I tell the team today".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Erica-J-01

Erica-J-01/ai-pm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

2 files

SKILL.md

readonly

name	sprint-report
description	Analyses Jira sprint data and produces a concise PM-ready report. Use whenever someone shares a sprint report, burndown chart, velocity chart, board screenshot, or Jira ticket data and wants to understand sprint health, delivery confidence, risks, blockers, or team performance. Trigger for phrases like "analyse this sprint", "what does the burndown say", "how is the sprint looking", "write up the sprint report", or "what should I tell the team today".
version	1.1.0
argument-hint	<sprint data, burndown, or Jira board link>
allowed-tools	Read, mcp__claude_ai_Atlassian_Rovo__searchJiraIssuesUsingJql, mcp__claude_ai_Atlassian_Rovo__getJiraIssue, mcp__claude_ai_Atlassian_Rovo__createConfluencePage, mcp__claude_ai_Atlassian_Rovo__getConfluenceSpaces

Input

$ARGUMENTS

If no input is provided above, ask: "Please paste your Jira sprint data - burndown, velocity, ticket statuses, or a screenshot description. Which day of the sprint are we on?"

Minimum viable inputs: committed vs done, plus the sprint day or days remaining. If a paste is missing either, ask once, then proceed with whatever the user provides. If days remaining are unknown, do not emit a confidence percentage - write "Sprint Confidence: not assessable without days remaining" instead. If no velocity history is given, state that the forecast is based on this sprint only.

If Jira is connected (pull path): ask for the project key and the sprint name or ID. Validate the project key against [A-Za-z0-9_]+ before building JQL. Pull status, assignee, story points, and flagged state for the sprint's issues. Caveat: a query of current issues cannot reliably reconstruct the committed baseline or mid-sprint scope adds, so ask the user for the commitment figure and the sprint day rather than inferring them from the current backlog.

If Jira is not connected (MCP tool unavailable): do not fabricate ticket data. Tell the user Jira isn't connected and ask them to paste the board state (ticket statuses, assignees, blockers). The report format is identical - only the data source changes. See Connection Failsafe in .claude/CLAUDE.md.

Prior report check: when the active client/project is known, look for an earlier dated report on the same sprint in clients/CLIENT/PROJECT/sprint-artefacts/. If one exists, read it and open the Executive Summary with the movement since then - confidence shift, blockers still open or unmoved, new risks. Never search across clients. If no prior report exists or the project is ambiguous, proceed as normal.

Assess: burndown trend, completed vs committed, sprint goal attainment, blocked/aging tickets, scope changes, QA bottlenecks, overloaded owners, and velocity trend.

Sprint mode: determine whether the sprint is in flight or closed - from the input ("Day 10 of 10", "sprint ended", past-tense data) or by asking once. For a closed sprint, keep the format below with two swaps: Forecast becomes actuals (completed vs committed, velocity achieved), and Actions Today plus Questions for Standup are replaced by a single Carry-over and Next Sprint Implications section covering which items carry over, where they land, and what that means for the next commitment. Everything else is unchanged.

MANDATORY OUTPUT FORMAT

Executive Summary

3 short sentences maximum.

Delivery Status

Status: Green / Amber / Red
Sprint Confidence: XX%
Forecast: X of Y items likely complete
Velocity: committed X vs ~Y trailing average - on trend / over-committed / under-committed (only when velocity history is provided)
Sprint goal: on track / at risk / missed - goal in a few words (if no goal was provided, write "not stated in input" - never invent one)
Risk: Low / Medium / High

Top 3 PM Priorities

Main Risks

Actions Today

Questions for Standup

Leadership Update

2 short professional sentences.

FINAL ACTION (MANDATORY)

After generating the report, ask the user where they want it saved:

"Where would you like me to save this? I can save it locally or push it directly to any platform you have connected via MCP."

Local

Local file - saved to clients/CLIENT/sprint-artefacts/YYYY-MM-DD-sprint-N-report.md

Connected platforms (via MCP) 2. Confluence - published as a new page (I'll ask for your domain, space, and parent page) 3. Google Drive - saved as a new Doc (I'll ask for the folder) 4. Notion - created as a new page (I'll ask for your workspace and parent page)

No save 5. Clipboard only - leave it here for you to copy manually

Do not save or publish anything until the user confirms the destination.

If Confluence is chosen:

Ask for the Confluence cloud domain, space key, and parent page title or ID
Resolve the space ID using getConfluenceSpaces if needed
Use createConfluencePage with:
- cloudId: as provided by the user
- spaceId: resolved from the space key
- parentId: as provided by the user
- title: {Project} Sprint Report - {Sprint Name}, Day {N} ({YYYY-MM-DD}) - for a closed sprint use Close-out in place of Day {N}
- contentFormat: markdown
- body: the full report markdown
Return the live Confluence page URL to the user

More from this repository

same repository

budget-tracker

Erica-J-01/ai-pm

Tracks project spend against the charter budget over time and flags burn-rate risk. Use whenever someone says "track the budget", "how much have we spent", "are we on budget", "burn rate", or shares cost/effort data that needs comparing to an approved budget. Produces a budget status with spent-to-date, forecast at completion, variance, and a RAG verdict. Not a charter - the charter sets the budget and this skill monitors it.

2026-07-126

project-charter

Erica-J-01/ai-pm

Turns a project brief, intake summary, or rough idea into a complete, sponsor-ready project charter. Use whenever someone says "write the charter", "start a new project", "formalise this project", "we need a charter", "draft the project document", or pastes a brief and needs it turned into an official document. Also triggers after an intake summary is complete and the next step is formal authorisation. A charter is the document that officially starts a project - without it, the PM has no authority to act and the team has no agreed scope. Use this skill early, before any planning begins.

2026-07-126

decision-log

Erica-J-01/ai-pm

Creates a structured decision log from project changes, scope revisions, or PM decisions. Use whenever a decision needs to be formally recorded - including when someone says "log this decision", "document this change", "we changed direction on X", or when the PM Orchestrator detects a decision in a prior skill output and asks whether to log it. Also triggers when a user shares a change request, revised scope, or any deviation from the original plan that needs an audit trail.

2026-07-126

discovery-workshop

Erica-J-01/ai-pm

Plans and documents discovery workshops and stakeholder interviews for new projects. Use whenever a PM needs to prepare for or capture output from a discovery session - including when someone says "plan a discovery workshop", "run discovery on this", "I need to interview stakeholders", "help me structure discovery", "summarise what came out of the discovery session", or shares raw notes from a workshop or interview and needs them turned into structured findings. Discovery is where projects are made or broken - the goal is to understand the real problem before anyone commits to a solution. Use this skill before requirements are written and before any build begins.

2026-07-126

meeting-notes

Erica-J-01/ai-pm

Use this skill whenever the user wants to extract meeting notes, minutes, or a summary from a meeting transcript - especially from Microsoft Teams, Zoom, Google Meet, or any raw transcript text. Trigger when the user shares a transcript file or text and asks for a summary, key points, action items, decisions, or meeting minutes. Also trigger when the user says things like "summarize this meeting", "what was discussed", "extract the important parts", "write up the minutes", or pastes a block of conversation text that looks like a meeting transcript. This skill produces clean, plain-English meeting minutes and follow-up questions the user can ask to go deeper. Also trigger when the user wants to save or publish meeting minutes to Confluence.

2026-07-126

prd

Erica-J-01/ai-pm

Writes a Product Requirements Document (PRD) or Business Requirements Document (BRD) from discovery findings, a project brief, or raw stakeholder input. Use whenever someone says "write the PRD", "write the BRD", "document the requirements", "turn this into a spec", or has completed discovery and needs requirements formally documented before build begins. A PRD defines what to build and why - from the product/user perspective. A BRD defines what the business needs the solution to achieve - from the business/stakeholder perspective. Both serve the same purpose: give the team a single agreed source of truth so everyone builds the same thing. Use this skill after discovery, before user stories or design begins.

2026-07-126

name	sprint-report
description	Analyses Jira sprint data and produces a concise PM-ready report. Use whenever someone shares a sprint report, burndown chart, velocity chart, board screenshot, or Jira ticket data and wants to understand sprint health, delivery confidence, risks, blockers, or team performance. Trigger for phrases like "analyse this sprint", "what does the burndown say", "how is the sprint looking", "write up the sprint report", or "what should I tell the team today".
version	1.1.0
argument-hint	<sprint data, burndown, or Jira board link>
allowed-tools	Read, mcp__claude_ai_Atlassian_Rovo__searchJiraIssuesUsingJql, mcp__claude_ai_Atlassian_Rovo__getJiraIssue, mcp__claude_ai_Atlassian_Rovo__createConfluencePage, mcp__claude_ai_Atlassian_Rovo__getConfluenceSpaces

Input

$ARGUMENTS

If no input is provided above, ask: "Please paste your Jira sprint data - burndown, velocity, ticket statuses, or a screenshot description. Which day of the sprint are we on?"

Assess: burndown trend, completed vs committed, sprint goal attainment, blocked/aging tickets, scope changes, QA bottlenecks, overloaded owners, and velocity trend.

MANDATORY OUTPUT FORMAT

Executive Summary

3 short sentences maximum.

Delivery Status

Status: Green / Amber / Red
Sprint Confidence: XX%
Forecast: X of Y items likely complete
Velocity: committed X vs ~Y trailing average - on trend / over-committed / under-committed (only when velocity history is provided)
Sprint goal: on track / at risk / missed - goal in a few words (if no goal was provided, write "not stated in input" - never invent one)
Risk: Low / Medium / High

Top 3 PM Priorities

Main Risks

Actions Today

Questions for Standup

Leadership Update

2 short professional sentences.

FINAL ACTION (MANDATORY)

After generating the report, ask the user where they want it saved:

"Where would you like me to save this? I can save it locally or push it directly to any platform you have connected via MCP."

Local

Local file - saved to clients/CLIENT/sprint-artefacts/YYYY-MM-DD-sprint-N-report.md

Connected platforms (via MCP) 2. Confluence - published as a new page (I'll ask for your domain, space, and parent page) 3. Google Drive - saved as a new Doc (I'll ask for the folder) 4. Notion - created as a new page (I'll ask for your workspace and parent page)

No save 5. Clipboard only - leave it here for you to copy manually

Do not save or publish anything until the user confirms the destination.

If Confluence is chosen:

Ask for the Confluence cloud domain, space key, and parent page title or ID
Resolve the space ID using getConfluenceSpaces if needed
Use createConfluencePage with:
- cloudId: as provided by the user
- spaceId: resolved from the space key
- parentId: as provided by the user
- title: {Project} Sprint Report - {Sprint Name}, Day {N} ({YYYY-MM-DD}) - for a closed sprint use Close-out in place of Day {N}
- contentFormat: markdown
- body: the full report markdown
Return the live Confluence page URL to the user