sprint-planning

Manage sprint planning with MoSCoW prioritization and GitHub milestones.

8|2|Updated Apr 16, 2026

Search Tags:#dependency analysis #sprint planning #milestone management #capacity estimation #MoSCoW prioritization

Ready to run

npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill sprint-planning-sebastiendegodez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/sprint-planning
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill sprint-planning-sebastiendegodez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps streamline the sprint planning process, ensuring that stories are prioritized correctly, capacity is estimated accurately, and dependencies are managed effectively.

Core Features & Use Cases

MoSCoW Prioritization: Use MoSCoW (Must, Should, Could, Won't) to prioritize stories effectively.
Milestone Management: Create and manage milestones following best practices for naming and scope.
Dependency Analysis: Build and validate dependency graphs to ensure smooth story sequencing.
Capacity Heuristics: Estimate available sprint capacity and ensure it aligns with planned story days.
GitHub Conventions: Apply GitHub labels and milestones to organize sprint planning.

Quick Start

Use the sprint-planning skill to prioritize your stories using MoSCoW and create a sprint plan for the next iteration.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema

How do I prioritize sprint stories using the MoSCoW method in GitHub?▼

Sprint story prioritization with MoSCoW categorizes stories into Must, Should, Could, and Won't buckets. This approach uses GitHub labels to organize and track story priority levels, ensuring the most critical features are addressed first within the sprint planning workflow.

What's the best way to manage dependencies and story sequencing for a software sprint?▼

Managing dependencies for a software sprint requires building and validating dependency graphs. This ensures smooth story sequencing by identifying blocking relationships between issues before the sprint begins, preventing development bottlenecks during the iteration.

How do I estimate sprint capacity for a development team?▼

Sprint capacity estimation calculates available working days against planned story days. It uses capacity heuristics to align team availability with the scoped workload, preventing overcommitment and ensuring the planned stories fit within the iteration's constraints.

Can I use GitHub milestones for sprint planning and scope management?▼

GitHub milestones support sprint planning by providing a structure for scope management. They can be created and managed following best practices for naming conventions, allowing teams to group related issues and track iteration progress directly within GitHub workflows.

Do I need knowledge of the software development lifecycle to plan sprints with GitHub?▼

Planning sprints effectively requires a solid understanding of software development lifecycle (SDLC) concepts and GitHub issue tracking. This foundational knowledge is necessary to apply prioritization techniques, manage milestones, and structure the sprint plan correctly.

Why does sprint planning fail when dependencies are not mapped?▼

Sprint planning fails without dependency mapping because untracked blockers disrupt story sequencing. Resolving dependencies beforehand by building a validated dependency graph ensures smooth execution and prevents development teams from stalling on incomplete prerequisites.