gds-sprint-status

Summarize sprint status and surface risks from Jira data into a concise report.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-sprint-status-joekhosbayar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-sprint-status
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-sprint-status
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-sprint-status-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates sprint data into a concise status overview, surfacing risks to keep stakeholders aligned and informed.

Core Features & Use Cases

  • Generate a clear status summary for stories and epics (backlog, in-progress, review, done) and highlight risks.
  • Surface recommended next actions and ownership to keep the sprint moving.
  • Provide an at-a-glance, shareable report suitable for stakeholders and leadership.

Quick Start

Ask the bot to run the sprint-status workflow for your current project to generate a status report.

Frequently Asked Questions about gds-sprint-status

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

FAQPage Schema
How do I generate a sprint status report from Jira issue-tracking data?

A sprint status report summarizes project data by consolidating stories and epics into a concise overview, validating status values against known sets, and flagging stale data to surface risks for stakeholders.

What is the best way to surface sprint risks and recommended next actions for stakeholders?

Surfacing sprint risks involves processing lightweight sprint artifacts to output recommended next actions with assigned owners, ensuring stakeholders remain aligned and informed.

Can I use this workflow to track agile project risks for stories in review or backlog?

Yes, you can track agile project risks by validating status values for stories across backlog, in-progress, review, and done states, then flagging stale data to highlight potential blockers.

Does this sprint summary workflow require any external dependencies or components to run?

No external dependencies or components are required; the workflow processes your existing Jira or lightweight sprint artifacts directly to produce a stakeholder-ready status report.

Why does my sprint status report show stale data instead of current project risks?

A sprint status report may show stale data when underlying issue-tracking data is outdated, which the workflow actively flags by validating status values against known sets during consolidation.