implement

# /implement - Autonomous Criteria-Driven Implementation

You are implementing a spec file autonomously. Work toward acceptance criteria (not steps), verify before declaring done, and cannot stop until verification passes or you properly escalate.

## Input

`$ARGUMENTS` = spec file path (REQUIRED)

Example: `/implement /tmp/spec-1234567890.md`

If no arguments: Output error "Usage: /implement <spec-file-path>"

## Process

### 1. Read and Validate Spec

Read the spec file from `$ARGUMENTS`:
- If file not found → output clear error and stop
- If file invalid (missing criteria section) → output clear error and stop

Extract:
- All criteria (AC-N, R-N, E-N)
- Verification methods for each
- Examples (accepted/rejected)
- Task-specific subagent definitions

### 2. Initialize

Create implementation log: `/tmp/implement-log-{timestamp}.md`

Write initial state:
```markdown
# Implementation Log

Spec: [spec file path]
Started: [timestamp]

## Criteria Status
- [ ] AC-1: [description]
- [ ] AC-2: [description]
- [ ] R-1: [description]
...

## Attempts
(will be filled as work progresses)
```

Create TodoWrite with criteria to satisfy:
```
- [ ] Create implementation log
- [ ] Satisfy AC-1: [brief description]; done when verified
- [ ] Satisfy AC-2: [brief description]; done when verified
- [ ] Satisfy R-1: [ensure not rejected]; done when verified
- [ ] (expand: sub-tasks as discovered)
- [ ] Call /verify when all criteria addressed
```

### 3. Work Toward Criteria

**CRITICAL: Work toward criteria, NOT steps.**

NO plan decomposition:
- Do NOT create plan files
- Do NOT chunk into "Chunk 1", "Chunk 2"
- Reference criteria IDs in your work

For each criterion:
1. Read the criterion and its verification method
2. Implement what's needed
3. Log attempt: "Tried X for AC-N, result: Y"
4. Make meaningful git commit referencing criterion
5. Move to next criterion

### 4. Log Before Proceeding

After each significant action, update `/tmp/implement-log-{timestamp}.md`:

```markdown