task-sizing

Enforce XS–XL task sizing and require breakdowns for L/XL tasks.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill task-sizing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-sizing
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/task-sizing
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill task-sizing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task sizing rules and mandatory breakdown requirements ensure sprint work is scoped, estimable, and manageable, preventing oversized tasks that stall progress.

Core Features & Use Cases

  • Sizing matrix and thresholds: defines XS, S, M, L, XL with explicit constraints
  • Enforcement discipline: planner MUST refuse to create L/XL tasks without breakdown
  • Examples and guidance: provides breakdown patterns to enable parallel work across teams

Quick Start

To apply the sizing rules, begin by breaking down large tasks into smaller, estimable units during sprint planning.

Frequently Asked Questions about task-sizing

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

FAQPage Schema
How do I prevent oversized tasks from stalling sprint planning?

Task sizing prevents oversized sprint work by applying an XS–XL sizing matrix with explicit constraints. Planners must refuse L/XL tasks without a mandatory breakdown, ensuring all sprint items remain scoped, estimable, and manageable.

What is the best way to break down large agile tasks for a sprint?

Breaking down large agile tasks involves applying an XS–XL sizing matrix and using provided example breakdown patterns. Large and extra-large tasks are split into smaller, estimable units to enable parallel work across teams during sprint planning.

How does the XS–XL task sizing matrix work in agile estimation?

An XS–XL task sizing matrix defines explicit size constraints for each tier from extra-small to extra-large. During sprint planning, any item estimated as L or XL triggers a mandatory breakdown requirement before it enters the sprint backlog.

Can I enforce mandatory task breakdowns during sprint planning?

Yes, enforcing mandatory task breakdowns during sprint planning requires applying guardrails that block L/XL work items. The sizing rules require explicit breakdown for large tasks and provide example patterns to enable parallel work across teams.

When should I apply task sizing guardrails in project management?

Task sizing guardrails should be applied during sprint planning, sprint start reviews, and task scoping when creating or reviewing work items. This enforces the XS–XL matrix and requires breakdown for any L/XL tasks to prevent stalled progress.