issue-size-estimation

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.

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.

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.

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.

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.