sprint-planning

Convert backlog items into prioritized user stories with acceptance criteria and sprint backlog.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill sprint-planning-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/sprint-planning
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill sprint-planning-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint & Release Planning removes ambiguity from planning ceremonies by turning vague priorities into clear, testable user stories, realistic estimates, and an executable sprint backlog so teams can commit with confidence and predictability.

Core Features & Use Cases

  • User story authoring: Produces INVEST-compliant stories with a three-scenario Given-When-Then acceptance criteria set and a concrete Definition of Done.
  • Estimation & decomposition: Breaks stories into independently testable tasks (≤4 hours each), recommends Fibonacci story points, and flags stories >8 points for splitting.
  • Release & roadmap planning: Generates release checklists, RICE-scored initiatives, and quarterly roadmap templates while mapping dependencies and quality gates.
  • Meeting facilitation: Suggests meeting agendas, timeboxed structures, and preparedness steps for product owners and engineering teams.

Quick Start

Create a two-week sprint plan for the next release by prioritizing the top backlog items, writing user stories with acceptance criteria and definition of done, estimating story points, and producing a sprint backlog and meeting agenda.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I write user stories with acceptance criteria for sprint planning?

User stories are written as INVEST-compliant items featuring a three-scenario Given-When-Then acceptance criteria set and a concrete Definition of Done to ensure testable sprint planning outcomes.

What is the best way to break down large backlog items into sprint tasks?

Break down backlog items by decomposing user stories into independently testable tasks under four hours each, applying Fibonacci story point estimates and splitting any stories estimated over eight points.

How does mapping dependencies work for release roadmap planning?

Release roadmap planning maps dependencies and quality gates by generating RICE-scored initiatives, quarterly roadmap templates, and release checklists to sequence committed sprint backlogs accurately.

Can I use this for backlog grooming and sprint meeting facilitation?

Yes, backlog grooming and meeting facilitation are supported through suggested timeboxed meeting agendas, preparedness steps, and prioritized sprint backlogs designed for Agile or Scrum teams.

When should large user stories be split during agile estimation?

During agile estimation, user stories exceeding eight Fibonacci story points should be split to maintain manageable scope, while all decomposed tasks must remain under four hours for independent testing.