# Sizing

> Sizing

- Skill: `wimpysworld/sizing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add wimpysworld/sizing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/wimpysworld/sizing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: wimpysworld (https://skillmd.com/u/wimpysworld)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/wimpysworld/sizing

---


# Sizing

One definition of the T-shirt scale. Size on what the work looks like, never on how long it might take.

## The scale

| Size | Points | What it looks like |
| ---- | ------ | ------------------ |
| XS | 1 | Trivial and self-evident. A config change, a docs fix, a small bug fix, a single-file edit. No design decision. |
| S | 2 | One focused slice, fully bounded. A standalone bug fix or feature slice with its own tests. Stays inside one module. |
| M | 3 | The workhorse. Clear scope, one owner, several files in one subsystem, with tests and docs. |
| L | 5 | The largest single unit. A new component, or a cross-cutting interface change with a settled design. |
| XL | 8 | Personal projects only. Never on work: split into a parent plus children. |

## Rules

- Index on what the work looks like, never on elapsed time. Do not estimate in days or weeks.
- Unresolved design is not a size, it is a spike. File the spike at XS or S, then size the real work once the design is settled.
- Parent tracking issues carry no estimate. The children carry the size.
- Work stops at L. Personal projects may use XL, but splitting is still the better move.
- Confirm the scale against the live workspace before assigning. The values above are what this workspace uses today, not a fixed truth.

## Telling the workspaces apart

The `WW` team, Wimpy's World, is personal. The `FUL` team, Fulfillment Automation, is work.

## Sprint loading

A human sanity check, not an agent input. A two-week sprint holds 8 XS, or 4 S, or 2 M, or 1 L.