feature-next

# Task Next

**One command**: `agent-foreman next`

## ⚠️ STRICT WORKFLOW - NO IMPROVISATION

**You MUST follow this exact sequence. Do NOT skip or reorder steps.**

```
next → implement → check → done
```

| ❌ FORBIDDEN | ✅ REQUIRED |
|--------------|-------------|
| Skip `check` step | Run `agent-foreman check` before `done` |
| Go straight to implementation | Run `agent-foreman next` first |
| Invent extra steps | Use only the 4 steps above |

## ⛔ CLI-ONLY ENFORCEMENT

**NEVER bypass CLI for workflow decisions:**

| ❌ FORBIDDEN | ✅ REQUIRED |
|--------------|-------------|
| Read `ai/tasks/index.json` to select task | Use `agent-foreman next` |
| Read `index.json` to check status | Use `agent-foreman status` |
| Read `index.json` for TDD mode | Check CLI output for `!!! TDD ENFORCEMENT ACTIVE !!!` |
| Edit task files to change status | Use `agent-foreman done/fail` |

**Allowed:** Reading task `.md` files for acceptance criteria AFTER running `agent-foreman next`.

---

## Quick Start

```bash
agent-foreman next           # Auto-select next priority
agent-foreman next auth.login  # Specific task
```

## Workflow

```
next → implement → check → done
```

```bash
agent-foreman next              # 1. Get task + acceptance criteria
# ... implement the task ...    # 2. Write code
agent-foreman check <id>        # 3. Verify implementation
agent-foreman done <id>         # 4. Mark complete + commit
```

### Check TDD Mode First

Look for "!!! TDD ENFORCEMENT ACTIVE !!!" in `agent-foreman next` output.

### TDD Workflow (when strict mode active)

```bash
# STEP 1: Get task + TDD guidance
agent-foreman next <task_id>

# STEP 2: RED - Write failing tests FIRST
# Create test file at suggested path
# Run tests: <your-test-command>
# Verify tests FAIL (confirms tests are valid)

# STEP 3: GREEN - Implement minimum code
# Write minimum code to pass tests
# Run tests: <your-test-command>
# Verify tests PASS

# STEP 4: REFACTOR - Clean up
# Clean up code while keeping tests pas