sprint-plan

Generate a structured sprint plan with tasks, criteria, dependencies, and risks.

5|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/rbah31/claude-code-workflow --skill sprint-plan-rbah31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/rbah31/claude-code-workflow/tree/main/.claude/skills/sprint-plan
Command: npx skills add https://github.com/rbah31/claude-code-workflow --skill sprint-plan-rbah31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning often stalls teams when backlog items lack structure. This Skill automates turning a backlog into a concrete sprint plan with clearly defined tasks, acceptance criteria, dependencies, and risks, enabling faster alignment and execution.

Core Features & Use Cases

  • Structured Plan: generates a sprint plan including goals, tasks, acceptance criteria, dependencies, and risk notes.
  • Backlog-to-Sprint Translation: converts backlog items into ready-to-work tasks suitable for the build phase.
  • Sprint Initialization: creates the new sprint directory tasks/sprints/sprint-XX and writes a plan.md.

Quick Start

Plan the next sprint by generating a complete plan from backlog inputs.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I turn a backlog into a structured sprint plan?

To turn a backlog into a structured sprint plan, you need backlog.md, lessons.md, and the latest retrospective files to automatically generate tasks, acceptance criteria, dependencies, and risks into a fixed plan.md output.

What is the best way to define tasks and acceptance criteria for a new sprint?

Defining tasks and acceptance criteria for a new sprint is best handled by translating backlog context into ready-to-work items, ensuring faster team alignment and execution through a clearly structured plan.

Do I need a retrospective file to generate a sprint plan?

Yes, generating a sprint plan requires the latest retrospective file along with backlog.md and lessons.md inputs to accurately map dependencies and risks for the upcoming sprint.

Can I use this sprint planning approach for any software project?

Yes, you can apply this sprint planning approach to new sprints across software projects, converting unstructured backlog items into concrete, executable tasks with associated risk notes.

Where does the generated sprint plan get saved?

The generated sprint plan gets saved directly to the repository by creating a new sprint directory at tasks/sprints/sprint-XX and writing the structured plan.md file there.

Will generating a sprint plan modify my existing repository files?

No, generating a sprint plan operates with a strict read-only policy on repository files, ensuring your existing inputs remain untouched while only writing the new plan.md output.