resume

# Resume The user got interrupted mid-/article (network blip, batch wait, laptop sleep, manual ctrl-C). This skill picks up where it left off. ## When to invoke - `/resume` (defaults to most-recent in-progress task) - `/resume <task_id>` (specific task) - After `/status` shows a stuck or stale task - Auto-suggest in error.json's recovery field ## How to invoke Step 1: Plan the resume (dry-run first) ```bash python -m scripts._core.resume_handler --task-id <id> --dry-run ``` This outputs: ``` ━━ Resume plan for abc123 ━━━━━━━━━━━━━━━━━ Currently at: build / image-generation-queued Will resume: build / images-injected ✓ Verified (2): • image_prompts.json • batch_id.json → Stage complete; jumping to next stage ETA: 18m42s Cost left: ~$0.74 Next: Re-invoke L2 phase 'build' for task abc123, resuming at stage 'images-injected'. ``` Step 2: Execute the resume Invoke the L2 phase orchestrator named by `next_phase` in the plan, with the task workspace pointing at the existing one: - `next_phase = research` → invoke `phase-research` SKILL with `--resume <task_id>` - `next_phase = plan` → invoke `phase-build` SKILL with `--resume <task_id>` - `next_phase = build` → invoke `phase-build` SKILL with `--resume <task_id>` - `next_phase = optimize` → invoke `phase-optimize` SKILL with `--resume <task_id>` - `next_phase = publish` → invoke `phase-publish` SKILL with `--resume <task_id>` - `next_phase = monitor` → invoke `phase-monitor` SKILL ...