sprint-planning

Create an executable Sprint from refined product backlog items with developer assignments.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill sprint-planning-sohei56
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/sohei56/maul-team/tree/main/skills/sprint-planning
Command: npx skills add https://github.com/sohei56/maul-team --skill sprint-planning-sohei56

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a refined product backlog into a well-scoped, executable Sprint while preventing assignment errors, dependency conflicts, merge risks, and unvalidated quality gates.

Core Features & Use Cases

  • Sprint Goal Approval: Proposes and validates a Sprint Goal with the Product Owner.
  • PBI Selection and Assignment: Selects refined PBIs, splits oversized work into vertical slices, and enforces a one-developer-per-PBI assignment model.
  • Conflict and Quality Planning: Analyzes catalog and source-file overlap, sequences risky work, configures merge regression gates, and prepares the Sprint for isolated implementation.
  • Use Case: Use this Skill after backlog refinement to create the next development Sprint, assign developers, update Scrum state, and prepare committed design scaffolding before implementation begins.

Quick Start

Use the sprint-planning skill to select the highest-priority refined PBIs, create the next Sprint, assign developers, and prepare the repository for implementation.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I assign developers to PBIs and prevent merge conflicts during sprint planning?

Sprint planning prevents merge conflicts by analyzing source-file overlap and enforcing a one-developer-per-PBI assignment model. This sequences risky work and configures merge regression gates to ensure isolated implementation.

What is the best way to split oversized product backlog items for a Scrum sprint?

Split oversized PBIs using vertical slicing during sprint planning to create executable development tasks. This prevents scope failures and dependency conflicts while maintaining alignment with the approved sprint goal.

Do I need Product Owner approval before creating a sprint from the product backlog?

Yes, Product Owner approval is required before creating a sprint. The process proposes and validates the sprint goal with the Product Owner before selecting refined PBIs, assigning developers, and preparing design scaffolding.

How do I configure quality gates and merge regression checks for a new sprint?

Configure quality gates by setting up merge regression checks during sprint planning. These checks must be explicitly configured or waived before implementation begins to prevent unvalidated scope and dependency failures.

Can I use automated sprint planning if my Scrum state files are not synchronized?

No, synchronized Scrum state and backlog files are required. The sprint planning process depends on these synchronized files to select refined PBIs, assign developers, and update the current sprint state accurately.

When should I not use automated PBI selection for sprint planning?

Avoid automated PBI selection without committed design scaffolding or if merge regression checks are neither configured nor explicitly waived. The process requires refined backlog items, Product Owner approval, and validated sprint goals.