scrum-event-sprint-planning

Select the top ready backlog item and define a sprint goal with TDD-style subtasks.

3|1|Updated Feb 3, 2012

Search Tags:#TDD #AI #sprint planning #backlog #subtasks #sprint-goal #PBI

Ready to run

npx skills add https://github.com/shishi/dotfiles --skill scrum-event-sprint-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scrum-event-sprint-planning
Source: https://github.com/shishi/dotfiles/tree/main/claude/skills/scrum-event-sprint-planning
Command: npx skills add https://github.com/shishi/dotfiles --skill scrum-event-sprint-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides AI teams through sprint planning by selecting the top ready backlog item (PBI) and defining a concrete sprint goal, ensuring alignment and focus.

Core Features & Use Cases

Sprint prioritization: automatically selects the highest-priority ready backlog item for the sprint.
Sprint Goal framing: defines a measurable goal based on the chosen PBI's benefits.
Subtask decomposition: breaks the sprint into small, testable subtasks following a TDD-style structure.

Use Case: When starting a sprint for an AI-enabled project, use this skill to produce a clear sprint goal and a first set of subtasks ready for execution.

Quick Start

Use the scrum-event-sprint-planning skill to guide the planning session: identify the top ready backlog item, define the sprint goal, and break it into subtasks in the format described in the Subtask Format section of the SKILL.md.

Frequently Asked Questions about scrum-event-sprint-planning

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

FAQPage Schema

How do I plan a sprint for an AI project using a ready backlog item?▼

To plan a sprint, select the highest-priority ready Product Backlog Item (PBI) and define a concrete, measurable sprint goal based on its benefits. This ensures alignment and focus before breaking the work down into subtasks for execution.

How does subtask decomposition work in a TDD-style sprint cycle?▼

Subtask decomposition breaks the selected sprint work into small, deterministic, and testable subtasks. This TDD-style structure ensures each subtask follows a specific schema, making the development cycle measurable and ready for execution.

What do I need to start sprint planning with a single source of truth?▼

You need a single source of truth file named scrum.ts and a YAML-formatted subtasks schema. These prerequisites ensure the sprint goal and the decomposed subtasks align with the project's defined structure and format.

Can I use this sprint planning approach for projects without a defined backlog?▼

No, you cannot use this approach without a defined backlog. The sprint planning process requires a ready backlog to automatically select the top priority Product Backlog Item (PBI) and frame the sprint goal.

What is the best way to frame a sprint goal for an AI-enabled project?▼

The best way to frame a sprint goal is to define a measurable objective derived directly from the chosen Product Backlog Item's benefits. This ensures the AI team maintains alignment and focus throughout the sprint execution.

Why does sprint planning require a YAML-formatted subtasks schema?▼

Sprint planning requires a YAML-formatted subtasks schema to standardize the breakdown of sprint work into deterministic, testable units. This format enforces the TDD-style cycle structure and ensures the generated subtasks are ready for execution.