sprint

Automate sprint planning by updating TASKS.md, CHANGELOG.md, and version placeholders.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mattpainter701/my-claude-setup --skill sprint-mattpainter701
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/mattpainter701/my-claude-setup/tree/main/claude-config/global-skills/sprint
Command: npx skills add https://github.com/mattpainter701/my-claude-setup --skill sprint-mattpainter701

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint lifecycle management. Open new sprints (create TASKS.md entries, version placeholder) or close sprints (verify completion, bump versions, archive, commit).

Core Features & Use Cases

  • Open sprints: create TASKS.md entries with sprint header and tasks, and bump version placeholders as needed.
  • Close sprints: verify all tasks are completed, bump versions, archive sprint data, and commit changes.
  • Integrates with project workflows by prompting for sprint goals, number of tasks, and per-task descriptions.

Quick Start

Open Claude and type /sprint open to begin a new sprint.

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 and lifecycle management?

Sprint lifecycle management automates sprint planning by reading TASKS.md and CHANGELOG.md, calculating the next sprint number, and updating version placeholders. It guides users through sprint goals and task descriptions to open sprints, and validates completion to close them.

How do I create and open a new sprint in markdown?

To open a new sprint, invoke the sprint open command. The workflow reads your existing TASKS.md, calculates the next sprint number and task IDs, and generates sprint headers with per-task descriptions by prompting you for sprint goals and task counts.

How does version bump detection work when closing a sprint?

Version bump detection during sprint close verifies all tasks are completed, checks version placeholders across files, and applies deterministic edits. It ensures consistent sprint records by validating completion, bumping versions, archiving sprint data, and committing changes.

Do I need a TASKS.md file to track sprint workflows?

Yes, a TASKS.md file is required. The workflow reads TASKS.md and CHANGELOG.md to calculate the next sprint number and task IDs, and updates version placeholders across files to maintain deterministic and consistent sprint records.

Can I use markdown files for project management versioning and task tracking?

Yes, you can use markdown files for project management versioning by maintaining TASKS.md for task entries and CHANGELOG.md for records. The workflow applies script-driven edits to update version placeholders, calculate task IDs, and archive completed sprints automatically.