sprint-planning

Plan sprint cycles by defining goals, selecting backlog items, and distributing work.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill sprint-planning-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/mahg-es/araya/tree/main/skills/sprint-planning
Command: npx skills add https://github.com/mahg-es/araya --skill sprint-planning-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning without structure leads to unclear goals, misaligned capacity, and hidden dependencies.

Core Features & Use Cases

  • Goal setting: defines a clear sprint objective.
  • Backlog selection: prioritizes items by value and dependencies.
  • Capacity alignment: assigns capacity per team member and computes total velocity.
  • Use Case: Imagine a team starting a 2-week sprint to deliver a user authentication feature with defined tasks and milestones.

Quick Start

Provide a sprint backlog with goals, capacity, and assignments for the upcoming sprint.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I plan a sprint cycle with capacity and velocity alignment?

Plan sprint cycles by defining a sprint goal, selecting prioritized backlog items, and distributing work based on team capacity. The process outputs a detailed sprint plan with aligned goals, total velocity, and a prioritized backlog.

What is the best way to select backlog items for a 2-week sprint kickoff?

Select backlog items by prioritizing them according to value and dependencies. This ensures the sprint goal remains clear and achievable while aligning assignments with available team capacity.

Do I need team capacity and velocity data to start sprint planning?

Yes, sprint planning enforces input requirements including backlog, capacity, velocity, and dependencies. Providing this data ensures accurate capacity alignment per team member and a realistic total velocity calculation.

Can I use this sprint planning process for cross-functional teams with varying backlog sizes?

Yes, this sprint planning process applies to regular planning sessions and project kickoffs across cross-functional teams. It handles varying backlog sizes by enforcing structured input requirements and capacity alignment.

Why does sprint planning fail without structured backlog and dependency enforcement?

Sprint planning without structure leads to unclear goals, misaligned capacity, and hidden dependencies. Enforcing input requirements prevents these issues by ensuring backlog selection is prioritized by value and dependencies.