iterative-development

# Iterative Development Skill

Supports adding deltas and analyzing impact without full upfront planning.

## When to Load

Load this skill for:
- `/katachi:add-delta` - Add new delta on-the-go
- `/katachi:analyze-impact` - Analyze change impact

## Dependencies

This skill requires `katachi:framework-core` to be loaded first for:
- Workflow principles
- Task management protocol
- Status tracking conventions

## Philosophy

The framework should support "add as you go" not "define everything upfront":

- Deltas can be added mid-project
- Dependencies are analyzed dynamically
- Quick-start mode for MVPs

## Add Delta Workflow

### 1. Capture Delta Description

Ask user to describe the delta:
- What does it do?
- Who uses it?
- Any known dependencies?

### 2. Assign ID

Deltas follow the pattern: `DLT-NNN`

**Process:**
1. Read existing deltas from DELTAS.md
2. Assign next available sequential ID
3. Confirm with user

```python
# Example categories (domain-oriented, organized by user capability area)
AUTH - Authentication flows (Login, Logout, Password Reset, Session Timeout)
USER - User management (Registration, Profile, Settings, Account Deletion)
ORDERS - Order management (Create Order, View Orders, Cancel Order)
PAYMENTS - Payment flows (Checkout, Refund, Payment Methods)
ADMIN - Admin capabilities (Manage Users, View Reports, System Settings)
CORE - Core infrastructure (when truly cross-cutting and not user-facing)
```

If new category needed, confirm with user before creating.

### 3. Assign ID

Find next available ID in category:

```bash
# Check existing IDs
python scripts/deltas.py status list --category CORE

# Result: CORE-001, CORE-002, CORE-003
# New ID: CORE-004
```

### 4. Capture Complexity

Ask user for complexity estimate:
- **Easy**: 1-2 hours, straightforward
- **Medium**: Half day, some complexity
- **Hard**: Full day+, significant complexity

### 5. Analyze Dependencies

**Option A: User knows dependencies**
- Ask: "Does this depend on any existin