sprint-update

Automate sprint document updates with merge results, persona statuses, and velocity metrics.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/tonykoop/claude-skills --skill sprint-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-update
Source: https://github.com/tonykoop/claude-skills/tree/main/plugins/coding/skills/sprint-update
Command: npx skills add https://github.com/tonykoop/claude-skills --skill sprint-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates updating sprint documents with new merge results, persona status changes, and velocity statistics to keep stakeholders aligned.

Core Features & Use Cases

  • Automatically refresh sprint headers with current PR counts, open issues, and velocity milestones.
  • Regenerate and organize dispatch prompts per persona for planned action rounds.
  • Maintain consistency across sprint artifacts after a batch of merges or sprint reviews.

Quick Start

Run the sprint-update tool to apply the latest changes to the active sprint document.

Frequently Asked Questions about sprint-update

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

FAQPage Schema
How do I automate sprint document updates after merging PRs?

Automating sprint document updates involves refreshing sprint headers with current PR counts, open issues, and velocity milestones. This process keeps stakeholders aligned by applying the latest merge results to the active sprint document.

What is the best way to track velocity metrics and persona status changes across multiple repos?

Tracking velocity metrics and persona status changes across multiple repos is done by summarizing PR activity to update sprint artifacts. This ensures consistency by producing up-to-date dispatch prompts for planned action rounds.

Can I use this to generate dispatch prompts for different personas during a sprint review?

Yes, you can generate dispatch prompts for different personas during a sprint review. The tool regenerates and organizes dispatch prompts per persona to maintain consistency across sprint artifacts after a batch of merges.

Does sprint update work without external dependencies or project management integrations?

Sprint update works without external dependencies, operating directly on sprint documents to apply merge results and velocity statistics. It functions independently to produce header counts and archive follow-ups for downstream actions.

When should I refresh sprint artifacts for project management tracking?

You should refresh sprint artifacts during sprint progression, after a batch of merges, or when summarizing PR activity across multiple repos. This timing ensures validation by producing up-to-date header counts and dispatch prompts.