issue-classification

# Issue Classification

Guide for configuring automatic classification of issues into problem classes.

## When to Use

- Setting up ADW issue routing
- Improving classification accuracy
- Handling edge cases in classification
- Designing custom problem classes

## Why Classification Matters

Classification routes issues to the correct template:

```text
Issue: "Login button not working"
  ↓
Classification: /bug
  ↓
Template: Bug fix plan with root cause analysis
```

Without classification, agents don't know which workflow to use.

## Standard Problem Classes

### Chore

Maintenance tasks, updates, cleanup:

```text
Examples:
- "Update dependencies to latest"
- "Clean up unused imports"
- "Rename function to follow convention"
- "Add missing documentation"

Signals:
- "update", "upgrade", "clean", "remove", "rename"
- "documentation", "comment", "format"
- No user-facing change
- Maintenance in nature
```

### Bug

Defects, errors, unexpected behavior:

```text
Examples:
- "Login form submits twice"
- "404 error on profile page"
- "Data not saving correctly"
- "Crash when clicking button"

Signals:
- "error", "bug", "fix", "broken", "crash"
- "not working", "fails", "incorrect"
- Something that worked before now doesn't
- Unexpected behavior
```

### Feature

New functionality, enhancements:

```text
Examples:
- "Add dark mode toggle"
- "Implement user authentication"
- "Create new dashboard page"
- "Add export to CSV"

Signals:
- "add", "create", "implement", "new"
- "enhance", "improve", "extend"
- User-facing new capability
- Didn't exist before
```

## Classification Command

### Basic Structure

```markdown
# Issue Classification

Analyze the issue and respond with exactly one of:
- `/chore` - maintenance, updates, cleanup
- `/bug` - defects, errors, unexpected behavior
- `/feature` - new functionality, enhancements

If the issue doesn't fit any category, respond with `0`.

## Issue
$ARGUMENTS
```

### Enhanced with Examples

```markdown
# Issue Classification