issue-size-estimation

Estimate GitHub issue size and complexity using code line criteria.

Updated Jan 8, 2026

Search Tags:#decomposition #issue tracking #github issues #agile development #code complexity #task estimation

Ready to run

npx skills add https://github.com/takemo101/compose-workflow --skill issue-size-estimation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-size-estimation
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/issue-size-estimation
Command: npx skills add https://github.com/takemo101/compose-workflow --skill issue-size-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers accurately estimate the size and complexity of GitHub issues, ensuring they are appropriately sized for implementation and preventing the creation of overly large or unmanageable tasks.

Core Features & Use Cases

Issue Decomposition: Provides clear criteria for when an issue needs to be broken down into smaller, more manageable tasks.
Size Labeling: Recommends a system of size labels (size/xs to size/xl) based on estimated code lines.
Estimation Guidance: Offers methods for estimating code lines based on issue labels, design documents, or keywords.
Use Case: Before starting development, a developer can use this Skill's guidelines to determine if a new issue is too large and needs to be decomposed using /decompose-issue before proceeding with /implement-issues.

Quick Start

Use the issue-size-estimation skill to determine if issue number 8 needs to be decomposed.

Frequently Asked Questions about issue-size-estimation

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

FAQPage Schema

How do I estimate the size and complexity of software development issues?▼

To estimate issue complexity, you can use criteria and methods that assess estimated code lines based on issue labels, design documents, or keywords. This helps determine appropriate size labels ranging from size/xs to size/xl for your tasks.

When do I need to decompose GitHub issues before starting development?▼

You should decompose GitHub issues when estimation criteria indicate the task is too large or unmanageable. If an issue exceeds the recommended code line thresholds for a specific size label, it needs to be broken down into smaller, manageable tasks before implementation.

What size labels should I use for agile development task estimation?▼

For agile development task estimation, a recommended system uses size labels from size/xs to size/xl. These labels categorize issue granularity based on the estimated lines of code required for implementation.

How do I estimate code lines for a new issue using design documents?▼

You can estimate code lines by analyzing issue labels, design documents, or keywords. The skill outlines specific strategies to leverage these inputs to forecast the code volume needed, ensuring the issue is appropriately sized for implementation.

Can I integrate issue size estimation directly into my development workflow?▼

Yes, you can integrate issue size estimation into your development workflow by evaluating issue complexity before proceeding. After estimating size, you can decide whether to use decompose-issue commands to break down tasks before running implementation commands.