sprint

Automate implement, review, and ship phases for issues in issues.md.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill sprint-pillip
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/sprint
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill sprint-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill autonomously manages the end-to-end sprint workflow for issues tracked in issues.md, ensuring consistent implement → review → ship progression and reducing manual handoffs.

Core Features & Use Cases

  • End-to-end pipeline: automatically conducts implement, review, and ship phases for backlog items in a single invocation, while enforcing mandatory sequencing.
  • Dynamic progress tracking: leverages docs/sprint_state.md to reflect real-time status, escalate bottlenecks, and log retries and escalations.
  • Safe parallelism and governance: respects --parallel and --max-iterations controls, uses a queue to avoid conflicts, and adheres to authentication and safety checks.

Quick Start

Run the sprint process to automatically manage backlog issues in issues.md by issuing the /sprint command.

Frequently Asked Questions about sprint

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

FAQPage Schema
How do I automate end-to-end sprint workflows for issues in markdown files?▼

Automating sprint workflows for issues tracked in issues.md requires enforcing a mandatory implement, review, and ship sequence. Using a dedicated automation skill handles dynamic backlog management and automatic follow-on issue creation while logging progress to sprint_state.md.

What is the best way to enforce implement, review, and ship sequencing for backlog issues?▼

Enforcing strict implement, review, and ship sequencing for backlog issues is achieved by applying phase control through a sprint_state.md file. This approach ensures safety checks and authentication are validated before progressing items through the pipeline automatically.

Can I run parallel sprint pipelines for multiple issues without causing conflicts?▼

Running parallel sprint pipelines for multiple issues is supported by utilizing a queue to avoid conflicts. You can configure execution using parallel and max-iterations controls, which respect safety checks and govern parallelism within the workflow.

Do I need a sprint_state.md file to track dynamic backlog progress?▼

A sprint_state.md file is required to track dynamic backlog progress and control sprint phases. It reflects real-time status, escalates bottlenecks, and logs retries and escalations, serving as the central state mechanism for issue lifecycle management.

How does automatic follow-on issue handling work in a markdown-based sprint pipeline?▼

Automatic follow-on issue handling in a markdown-based sprint pipeline works by dynamically managing the backlog after shipping an item. The automation evaluates the issues.md file and generates subsequent tasks to maintain continuous workflow progression.