complexity-scorer

Assess task descriptions to assign a 1-10 complexity score with split recommendations.

Updated Jan 29, 2026

Search Tags:#planning #complexity #engineering #scoring #risk-assessment #task-splitting

Ready to run

npx skills add https://github.com/qazuor/claude-code-plugins --skill complexity-scorer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: complexity-scorer
Source: https://github.com/qazuor/claude-code-plugins/tree/main/plugins/task-master/skills/complexity-scorer
Command: npx skills add https://github.com/qazuor/claude-code-plugins --skill complexity-scorer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically assesses a task's complexity and flags when decomposition is required to help teams plan work more predictably.

Core Features & Use Cases

8-factor scoring across files affected, dependencies, testing needs, risk, architectural impact, data model changes, API surface, and cross-cutting concerns.
Enforces a hard ceiling of 4 for atomic tasks and provides split recommendations for higher scores.
Generates a decomposition plan and communicates actionable next steps to engineers.

Quick Start

Provide a task description and project context to obtain a 1-10 complexity score plus a split recommendation if needed.

Frequently Asked Questions about complexity-scorer

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

FAQPage Schema

How do I score task complexity for software engineering planning?▼

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.

When do I need to split tasks during project scoping?▼

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.

What factors are assessed in engineering risk assessment for task decomposition?▼

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.

How do I generate a decomposition plan for complex engineering tasks?▼

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.

What is the maximum complexity score for an atomic task before decomposition is required?▼

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.

Can I use complexity scoring to allocate engineering effort across a project?▼

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.