sprint-replayer

Reconstruct sprint cycle timelines from archived state.json, logs, and reviews.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill sprint-replayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-replayer
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/sprint-replayer
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill sprint-replayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconstructs sprint cycle timelines from archived data to enable replay, analysis, and auditing of past iterations.

Core Features & Use Cases

  • Rebuilds chronological event streams from archived sprint data, including state.json snapshots, tool-history logs, retrospectives, and reviews.
  • Supports /sprint:replay and /sprint:fork workflows by producing consistent cycle timelines for reanalysis.
  • Useful for debugging sprint planning errors, validating historical DoD, and generating replayable records for governance.

Quick Start

Run the sprint-replayer against the archive for a specific cycle to generate a chronological event stream.

Frequently Asked Questions about sprint-replayer

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

FAQPage Schema
How do I reconstruct a sprint timeline from archived agile data?

You can reconstruct a sprint timeline by running the sprint-replayer against an archived cycle. It reads state.json, tool-history.log, sprint-*.md, and retrospective.md to produce a chronological event stream for replay and auditing.

What is sprint replay and when do I need it for release planning?

Sprint replay is the process of rebuilding chronological event streams from archived sprint data. You need it for retrospectives, release planning, and governance when validating historical definitions of done or debugging sprint planning errors.

Can I audit past iterations using sprint archives and tool-history logs?

Yes, you can audit past iterations by processing sprint archives and tool-history logs. The replayer consolidates state.json snapshots, reviews, and retrospective files to generate a replayable chronological record for governance.

What file formats do I need to rebuild agile cycle timelines from an archive?

To rebuild agile cycle timelines, you need state.json snapshots, tool-history.log files, sprint-*.md documentation, and retrospective.md files. These archive sources are parsed to generate the chronological event stream.

Does sprint-replayer work with existing retrospective and review files?

Yes, sprint-replayer processes existing retrospective.md and review files alongside state.json and tool-history.log. It integrates these archive sources to output a consistent cycle timeline for reanalysis.

What are the limitations of rebuilding sprint timelines from archived data?

Rebuilding sprint timelines relies entirely on archived data sources like state.json and tool-history.log. If these files are incomplete or missing from the archive, the chronological event stream cannot be fully reconstructed for retrospective analysis.