task

# Task

## Purpose

Structured implementation methodology for non-bugfix work (features, chores, refactors, docs). Ensures work is properly scoped, planned, implemented with proper patterns, and verified before completion.

## When to Use

- Implementing new features
- Refactoring existing code
- Adding documentation
- Chore/maintenance tasks

## Quick Reference

- **Setup**: `/task configure` (run once during framework setup)
- **Usage**: Invoked by workflow skill for non-bugfix work
- **Update**: `/task learn <path>` (analyze specific patterns)

### Config Location

Config path depends on how the plugin was installed:

| Plugin Scope | Config File | Git |
|--------------|-------------|-----|
| **project** | `.claude/skills/task.yaml` | Committed (shared) |
| **local** | `.claude/skills/task.local.yaml` | Ignored (personal) |
| **user** | `.claude/skills/task.local.yaml` | Ignored (personal) |

**Precedence when reading** (first found wins):
1. `.claude/skills/task.local.yaml`
2. `.claude/skills/task.yaml`
3. Skill defaults

## Modes

| Mode | Trigger | Purpose |
|------|---------|---------|
| **configure** | `/task configure` | Auto-detect project structure, test patterns, architecture |
| **learn** | `/task learn <path>` | Learn patterns from specific directory |
| **execute** | Via workflow | Execute task phases (default) |

## Discovery Process

During `/task configure`:
1. Scan project structure for architecture patterns
2. Identify test framework and testing conventions
3. Detect code style and file organization
4. Find common patterns for each layer
5. Save to `.claude/skills/task.yaml`

## Phases Overview

- **Phases**: Scope → Plan → Implement → Verify
- **Key Rule**: Understand before building
- **Output**: Working implementation with tests passing

## Task Phases

```
┌─────────────────────────────────────────────────────────────────────────────┐
│                           TASK WORKFLOW                                      │
├───────────────────────────