sprint-planning

Analyze sprint capacity and prioritize Jira or Linear backlog items.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/webrix-ai/agent-skills --skill sprint-planning-webrix-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/webrix-ai/agent-skills/tree/main/skills/sprint-planning
Command: npx skills add https://github.com/webrix-ai/agent-skills --skill sprint-planning-webrix-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the manual effort of planning a sprint by turning team capacity, backlog priorities, and workload constraints into a clear recommended scope.

Core Features & Use Cases

  • Capacity Analysis: Calculates available engineer-days while accounting for PTO, meetings, and team size.
  • Backlog Prioritization: Ranks work by priority, dependencies, effort, and sprint goals.
  • Workload Balancing: Distributes tasks across team members to avoid overcommitment and improve assignment fairness.
  • Use Case: A delivery lead can use this Skill before sprint kickoff to decide which Jira or Linear tickets fit the team’s realistic velocity and who should own each item.

Quick Start

Ask the Skill to plan the next sprint for your team using your backlog, capacity, and velocity data from Jira or Linear.

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 based on team capacity and backlog priority?

Sprint planning based on team capacity requires calculating available engineer-days against backlog priorities. This Skill analyzes team availability, dependencies, and velocity data to recommend a realistic sprint scope while balancing workload across engineers.

Can I use my Jira or Linear backlog to calculate sprint capacity?

Yes, you can use Jira or Linear backlog data for sprint capacity analysis. The Skill ingests your backlog items, team availability, and velocity metrics to compare target points against available engineer-days and generate a recommended sprint plan.

How do I balance workload across engineers during sprint planning?

Workload balancing during sprint planning prevents overcommitment by distributing tasks based on engineer availability. The Skill assigns backlog items across team members while accounting for PTO, meetings, and individual capacity to ensure fair task ownership.

What is the best way to prioritize backlog items for an upcoming sprint?

The best way to prioritize backlog items is ranking them by priority, dependencies, effort, and sprint goals. This Skill evaluates your backlog against these constraints to recommend which tickets fit your team's realistic velocity.

Does sprint planning work for engineering teams tracking velocity in story points?

Yes, sprint planning works for engineering teams tracking velocity in story points. The Skill compares your target story points against available engineer-days, factoring in PTO and meeting time, to recommend a balanced and realistic sprint scope.

Why does my sprint scope exceed the team's available engineer-days?

Your sprint scope exceeds available engineer-days when backlog prioritization ignores team capacity constraints. This Skill calculates realistic capacity by accounting for PTO and meetings, then recommends a balanced scope to prevent overcommitment.