workload-balance

Compute per-person active tickets and story points to detect workload imbalance.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/yannmenec/delivery-management-skills --skill workload-balance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workload-balance
Source: https://github.com/yannmenec/delivery-management-skills/tree/main/archive/v1/skills/sprint-operations/workload-balance
Command: npx skills add https://github.com/yannmenec/delivery-management-skills --skill workload-balance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects uneven distribution of in-progress work across team members and flags overloaded or underloaded individuals to prevent bottlenecks and burnout.

Core Features & Use Cases

  • Per-person workload calculations: active tickets, active story points, total assigned, and blocked tickets per member.
  • Imbalance detection: identifies Overloaded, Underloaded, Blocked, and Idle states with concrete recommendations.
  • Unassigned work detection: surfaces unassigned work and guidance to rebalance sprint capacity.

Quick Start

Provide sprint_tickets and team_members data to generate the workload report.

Frequently Asked Questions about workload-balance

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

FAQPage Schema
How do I detect uneven sprint workload across my team members?

Sprint workload imbalance is detected by computing each person's active tickets and story points against the team average to identify overloaded, underloaded, or idle members.

How do I generate a workload report for mid-sprint health checks?

To generate a workload report, provide your sprint tickets and team members data to calculate active story points and surface unassigned work for rebalancing sprint capacity.

What is the best way to prevent team overload during sprint planning?

Preventing team overload during sprint planning involves analyzing per-person capacity by checking assigned tickets and story points to flag individuals exceeding the average workload.

Can I identify unassigned work and blocked tickets during capacity reviews?

Capacity reviews can identify unassigned work and blocked tickets by evaluating total assigned tickets per member, providing guidance to rebalance sprint capacity and prevent bottlenecks.

Do I need specific data formats to calculate active story points per person?

Calculating active story points per person requires providing your sprint tickets and team members data to compute the structured workload report for the sprint.