complexity-scorer

Task complexity scoring evaluates factors like files affected, dependencies, testing needs, risk, architectural impact, data model changes, API surface, and cross-cutting concerns to assign a quantified 1-10 score. Provide a task description and project context to obtain the score.

Task splitting is needed when a complexity score exceeds four, which is the enforced ceiling for atomic tasks. The scoring process flags higher scores and automatically provides split recommendations to guide decomposition and effort allocation.

Engineering risk assessment evaluates eight factors: files affected, dependencies, testing needs, risk, architectural impact, data model changes, API surface, and cross-cutting concerns. These factors determine the 1-10 complexity score and subsequent decomposition plan.

To generate a decomposition plan, provide a task description and project context to the complexity scorer. It assigns a 1-10 score, and if it exceeds four, returns a split recommendation with structured guidance and actionable next steps for engineers.

The maximum complexity score for an atomic task is four. Any task scoring above this hard ceiling receives a split recommendation, ensuring predictable work planning by guiding when and how to decompose tasks.

Complexity scoring applies to software engineering planning and project scoping by quantifying task difficulty. It guides effort allocation by returning a 1-10 score and actionable next steps, helping teams plan work more predictably.