sprint

Automates end-to-end sprint cycles coordinating WORK, PLAY, and PLAN phases with CI validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end sprint workflow, coordinating WORK, PLAY, and PLAN to reduce manual overhead and miscommunication.

Core Features & Use Cases

  • Automates end-to-end sprint cycles across WORK, PLAY, and PLAN with autonomous batch execution.
  • Provides CI-validated handoffs between phases and deterministic outputs for backlog, defects, and plans.
  • Use Case: For a software team needing consistent sprint execution without manual prompts.

Quick Start

Initiate a full sprint cycle by triggering WORK, then PLAY, then PLAN to drive backlog processing, defect discovery, and planning through the Task tool.

Frequently Asked Questions about sprint

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

FAQPage Schema
How do I automate an end-to-end sprint workflow for software development?

Automate an end-to-end sprint workflow by triggering coordinated WORK, PLAY, and PLAN phases to drive backlog processing, defect discovery, and planning through autonomous batch execution. This reduces manual overhead and miscommunication across the sprint cycle.

What is autonomous batch execution in sprint planning and how does it work?

Autonomous batch execution in sprint planning runs the full cycle without user prompts. It uses Task tool integration for phase handoffs and requires CLAUDE.md rule sets to enforce deterministic outputs for backlog, defects, and plans.

How do I run a full sprint cycle with CI-validated handoffs between phases?

Run a full sprint cycle with CI-validated handoffs by sequentially executing the WORK, PLAY, and PLAN phases. The Task tool coordinates these phase transitions to ensure continuous integration validation across backlog items, issues, and tasks.

Do I need CLAUDE.md rule sets to automate defect discovery and backlog processing?

Yes, you need CLAUDE.md rule sets to automate defect discovery and backlog processing. These rule sets are required to enforce autonomous batch execution and ensure deterministic outputs during the WORK and PLAY phases without manual user prompts.

What's the best way to coordinate sprint phases without manual prompts?

The best way to coordinate sprint phases without manual prompts is using an automated workflow tool that applies CI validation across batch execution. Sequentially triggering WORK, PLAY, and PLAN ensures consistent sprint execution and deterministic planning outputs.