size

What it does

/cl-dev:size looks at a spec'd issue and gives it a complexity rating on a simple XS–XL scale (extra-small through extra-large), then records that rating on the issue itself. It gives you and your team a quick, consistent read on how much work an issue involves before anyone commits to building it. That helps with planning, prioritizing, and spotting issues that are too big and should be split up.

When to use it

Reach for /cl-dev:size once an issue has been written up with clear acceptance criteria, typically right after /cl-dev:spec and before you claim it and start work. It fits naturally alongside /cl-dev:backlog when you're triaging and prioritizing a set of open issues and want a complexity signal on each one.

Good moments to size an issue:

• After spec'ing a new feature, enhancement, bug, or refactor, to set expectations before planning.
• While grooming the backlog, to compare issues and decide what to pick up next.
• When an issue feels large and you want a clear signal that it should be broken into smaller pieces.

How to invoke it

Run the command in your coding agent, pointing it at the issue you want to size:

/cl-dev:size

Tell it which issue to assess (for example, by issue number or title) if it isn't already clear from your current context. The issue should already be spec'd, so there's enough detail to judge its complexity. When the skill finishes, the XS–XL rating is saved on the issue, ready for planning and prioritization.