# Rig Lifecycle

Use when reasoning about the rig lifecycle operations family (create / start / stop /...

- Repository: https://github.com/mvschwarz/openrig (8541 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mvschwarz/openrig --skill rig-lifecycle -g -a claude-code -y`
Codex: `npx skills add mvschwarz/openrig --skill rig-lifecycle -g -a codex -y`
Cursor: `npx skills add mvschwarz/openrig --skill rig-lifecycle -g -a cursor -y`
Gemini CLI: `npx skills add mvschwarz/openrig --skill rig-lifecycle -g -a gemini-cli -y`

## Description

Use when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / lifecycle projections after recovery, or designing proof for a lifecycle scenario. Covers the 4 failure modes (auto-restore creates partial rig; projections report healthier than reality; provider auth treated as impl work; resume succeeds for one runtime fails another) plus the restore-honesty rule (failed resume is FAILED loudly, no auto fresh fallback).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Rig Lifecycle

The family of operations that **create, start, stop, resume, restore,
snapshot, release, unclaim, and destroy** OpenRig-managed topologies.
Includes the user story after reboot: **"bring my work back without
turning a clean recovery into a cleanup project."**

If lifecycle is brittle, every higher-level primitive inherits that
brittleness. Queue, workflow, seat continuity, cross-host operation,
and RSI all assume that rigs and seats can be restored into known
states.

## Use this when

- Operating `rig up / down / restore / resume / snapshot / release / unclaim / destroy`
- Reading `rig ps` after a reboot or recovery and deciding what to trust
- Designing proof for a lifecycle scenario (clean start / warm resume / host reboot / provider auth loss / partial boot / operator recovery)
- Reasoning about restore-outcome semantics (`resumed` / `rebuilt` / `fresh` / `failed` / `attention_required`)
- Auditing whether a lifecycle proof is in-process bedrock vs requires real reboot evidence

## Don't use this when

- The operation is single-command and deterministic, use `openrig-user` skill for CLI surface
- The work is operator-level configuration or troubleshooting of OpenRig itself, run `rig context get help`
- The work is rig spec authoring, use `openrig-architect`

## Failure modes (4)

The rest: https://github.com/mvschwarz/openrig/blob/HEAD/packages/daemon/specs/agents/shared/skills/core/rig-lifecycle/SKILL.md