assess-complexity

# Assess Complexity

Evaluate task complexity using automated codebase analysis before starting implementation work.

## Overview

- Determining if a task is ready for implementation
- Deciding whether to break down a large task
- Estimating effort before committing to work
- Identifying high-risk areas in the codebase
- Planning sprint work with complexity scores

## Usage

Assess complexity for: **$ARGUMENTS**

## Step 1: Gather Metrics

Run the analysis script to collect codebase metrics:

!`./scripts/analyze-codebase.sh $ARGUMENTS`

## Step 2: Assess Each Criterion

Score each criterion from 1-5 based on the metrics and your understanding:

### 1. Lines of Code

| Range | Score |
|-------|-------|
| < 50 lines | 1 |
| 50-200 lines | 2 |
| 200-500 lines | 3 |
| 500-1500 lines | 4 |
| 1500+ lines | 5 |

### 2. Time Estimate

| Duration | Score |
|----------|-------|
| < 30 minutes | 1 |
| 30 min - 2 hours | 2 |
| 2-8 hours | 3 |
| 8-24 hours (1-3 days) | 4 |
| 24+ hours (3+ days) | 5 |

### 3. Number of Files

| Count | Score |
|-------|-------|
| 1 file | 1 |
| 2-3 files | 2 |
| 4-10 files | 3 |
| 11-25 files | 4 |
| 26+ files | 5 |

### 4. Dependencies Count

| Unique Modules | Score |
|----------------|-------|
| 0 dependencies | 1 |
| 1 dependency | 2 |
| 2-3 dependencies | 3 |
| 4-6 dependencies | 4 |
| 7+ dependencies | 5 |

### 5. Unknowns/Uncertainty

| Level | Score |
|-------|-------|
| No unknowns - Everything clear | 1 |
| Minimal - 1-2 minor questions | 2 |
| Some - Several questions, researchable | 3 |
| Significant - Many questions, requires exploration | 4 |
| Many - Unclear scope, needs prototyping | 5 |

### 6. Cross-Cutting Concerns

| Scope | Score |
|-------|-------|
| Isolated change - Single module | 1 |
| Minor integration - 2-3 modules | 2 |
| Multiple integrations - 4-5 modules | 3 |
| Cross-cutting - Affects many modules | 4 |
| Architectural - System-wide impact | 5 |

### 7. Risk Level

| Risk | Score |
|------|-------|
| No risk - Tri