skills.rest
BrennonTWilliams
BrennonTWilliamsCOMMUNITY
Explore all skills by this author →
GitHub

issue-size-review

Evaluate issue complexity and decompose oversized tasks into child issues.

7|2|Updated Jan 3, 2026
Search Tags:#automation#refinement#decomposition#complexity#backlog#sprint
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill issue-size-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-size-review
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/issue-size-review
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill issue-size-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of oversized tasks that stall development, helping teams maintain momentum by breaking down complex work into manageable, independently shippable units.

Core Features & Use Cases

  • Complexity Scoring: Automatically evaluates issues based on file count, section complexity, and dependencies to identify those requiring decomposition.
  • Automated Decomposition: Proposes structured child issues with clear acceptance criteria, preserving context and scope.
  • Sprint Audit: Allows for targeted reviews of specific sprints or the entire backlog to ensure readiness and prevent context exhaustion.

Quick Start

Invoke the issue size review skill to audit the current backlog and decompose any oversized issues.

Frequently Asked Questions about issue-size-review

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

FAQPage Schema
How do I decompose large backlog issues into shippable units?▼

Automated backlog complexity scoring evaluates software development issues by analyzing file counts, section complexity, and dependencies to identify oversized tasks before they stall development momentum.

How do I audit sprint readiness for complex tasks?▼

You can audit sprint readiness by running a targeted review of specific sprints or the entire backlog to evaluate issue complexity and prevent context exhaustion during development cycles.

Do I need git and issue tracking integration to score issue complexity?▼

Yes, integrating with git and issue tracking systems is required to perform automated size scoring, update frontmatter, and create child issues during backlog refinement workflows.

What is the best way to prevent context loss during backlog refinement?▼

The best way to prevent context loss during backlog refinement is to automate the decomposition of oversized tasks into smaller, independently shippable units that preserve structured scope and acceptance criteria.

Why does automated decomposition create child issues during sprint planning?▼

Automated decomposition creates child issues during sprint planning to break down complex work into manageable units, preventing oversized tasks from stalling development and maintaining team momentum.

Related Skills

Explore More Software Engineering Skills→
michsindlingermichsindlinger
1

backlog-organization

Organize product backlogs with MoSCoW prioritization and sprint planning.

Community
Intermediate
proffesor-for-testingproffesor-for-testing
43

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning.

Community
Intermediate
nguyennd93nguyennd93

story-done

Automates story completion reviews by validating acceptance criteria and updating project management tools.

Community
Advanced
dividedbydividedby
1

triage

Manage GitHub issue lifecycles with a structured state machine via the gh CLI.

Community
Advanced