sprint

Pull Jira sprint state, calculate capacity, and generate a sprint backlog.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill sprint-scripsteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/Scripsteam/scrips-stack/tree/main/sprint
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill sprint-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Jira sprint ceremonies (planning, demo prep, and retro) without relying on memory or manual notes, ensuring the team always acts on current data.

Core Features & Use Cases

  • Pull current sprint state from Jira to assess open stories, estimates, and blockers
  • Generate a sprint backlog with a clear sprint goal and committed vs. stretch items
  • Prepare a sprint demo script and a retro-health checklist for stakeholders
  • Kick off or adjust sprint planning based on live Jira data and team capacity

Quick Start

Plan the current sprint using Jira data and prepare a backlog, sprint goal, and demo script.

Frequently Asked Questions about sprint

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

FAQPage Schema
How do I automate sprint planning using live Jira data?▼

Sprint planning with Jira data pulls your current sprint state to calculate team capacity and generate a backlog with committed and stretch items. It uses live Jira issues instead of manual notes to ensure accurate team coordination.

What is the best way to prepare a sprint demo from Jira tickets?▼

Preparing a sprint demo from Jira tickets generates a script outline based on completed stories in the current sprint. It extracts the sprint state automatically so stakeholders receive a structured presentation without manual data entry.

Can I generate a sprint backlog and goal directly from current Jira issues?▼

Yes, generating a sprint backlog from current Jira issues assesses open stories, estimates, and blockers to define a clear sprint goal. It separates committed work from stretch items to guide team capacity and planning.

How does a retro health check work with Jira sprint data?▼

A retro health check with Jira sprint data evaluates the completed sprint state to provide a checklist for stakeholders. It reviews open stories, estimates, and blockers to identify team coordination issues without relying on memory.

Do I need Jira to run sprint ceremonies and generate a demo script?▼

Yes, you need Jira to run these sprint ceremonies because the process pulls live sprint state, estimates, and blockers directly from Jira data. It does not use manual notes or memory to generate the backlog or demo script.