iterate

The user wants to iterate on: $ARGUMENTS

Determine the topic slug (short kebab-case, 3-5 words max).

Check if work/<slug>/ already exists.
- If it exists, look for plan.txt and iterations/ to resume where we left off.
  Read the plan and the latest iteration file to understand current state.
- If it exists but has only a brainstorm.txt, read that for context before starting.
- If work/<slug>/ doesn't exist, create it.

Create (if not already present):
  work/<slug>/plan.txt
  work/<slug>/iterations/

## plan.txt format

Keep this SHORT. High level only. Update it as understanding evolves.

```
ITERATION PLAN: <goal>
DATE STARTED: <date>

## Goal

<1-3 sentences on what we're trying to achieve>

## Approach

- <high level step 1>
- <high level step 2>
- ...

## Current Status

<where we are right now>
```

## Iteration file format

Each iteration goes in its own numbered file: iterations/01.txt, iterations/02.txt, etc.

```
ITERATION <number>
DATE: <date>

## What Was Done

<description of what was attempted>

## Result

<what happened - observations, outputs, errors, successes>

## Suggested Next Step

<what should be tried next based on what was learned>
```

## Workflow

1. If resuming, read the latest iteration's suggested next step and discuss with the user
2. If starting fresh, discuss the goal and write the initial plan.txt
3. Do the work (write code, run commands, whatever the iteration requires)
4. After each meaningful unit of work, write an iteration file capturing what happened
5. Update plan.txt's Current Status section
6. Ask the user if they want to continue to the next iteration or stop here