long-run-implement

# Long-Run Implement

Transform task specifications into executable plans and run them autonomously with minimal checkpoints, per-task atomic commits, and full state persistence.

## Usage

```
/long-run-implement [spec-path] [--prepare-only]
```

### Flags

- `--prepare-only`: Stop after Phase 2 (plan preparation). Use to review generated plans before execution.

## When to Use This Skill

Activate when the user says things like:
- "Implement this plan autonomously"
- "Run long-run implementation"
- "Execute these tasks with minimal interruption"
- "Implement the spec with atomic commits"

## What This Skill Does

1. **Initialize** - Set up or restore execution state
2. **Prepare Plans** - Call plan-fixer to validate, optimize, and split into individual plans
3. **Execute** - **Spawn fresh subagent per plan** via Task tool (preserves quality)
4. **Finalize** - Present summary and verification options

## Architecture: Fresh Context Per Plan

**CRITICAL**: This skill spawns a **fresh subagent for each plan** to prevent context degradation.

```
long-run-implement (orchestrator - stays in main context)
    │
    ├── Plan 01 → Task tool → fresh subagent (0% context) → executes → returns
    │                              ↑
    │                         200k tokens available
    │
    ├── Plan 02 → Task tool → fresh subagent (0% context) → executes → returns
    │
    └── Plan 03 → Task tool → fresh subagent (0% context) → executes → returns
```

Why this matters:
- **0-30% context**: Peak quality
- **30-50% context**: Good quality
- **50-70% context**: Degrading quality
- **70%+ context**: Poor quality

Each plan executes at peak quality because it starts fresh.

## Key Features

- **Fresh Context Per Plan** - Each plan spawns a new subagent with 200k tokens at 0%
- **Minimal Checkpoints** - Only stops for genuine blockers (architectural changes, external actions, unrecoverable errors)
- **Per-Task Atomic Commits** - Each completed task is committed immediately with c