▸ Control primitivesv0.1.1

checkpoint-resume

Persists long-run state to disk so a fresh session skips verified work already completed.

WORKFLOW / 05/checkpoint-resume <run label, or a path/id to resume>
  1. 01

    Decide new run or resume before touching state.

  2. 02

    Initialize through the locked checkpoint CLI; never overwrite a live run.

  3. 03

    Persist truthful phase and unit transitions as work lands.

  4. 04

    On resume, load disk state and rebuild only non-done eligible units.

  5. 05

    Finalize honestly and expose status through the read-only viewer.

▸ operating envelope

Use it deliberately.

The shortest useful definition of where this skill helps—and where it should stay out of the way.

Use when

  • A run has many independently identifiable units.
  • Interruption, crash, or session loss should not restart completed work.
  • Operators need a read-only view of live and terminal run state.

Do not use when

  • The task is a single indivisible action.
  • Units cannot be identified or verified independently.
  • You intend to use checkpoint writes as a delivery gate.

▸ output contract

What must be true when it stops.

Produces

  • .ulpi/runs/<id>.json durable state
  • Per-phase and per-unit timestamps and status
  • Open-item and needs-attention register
  • Read-only rendered status and resume command

Guarantees

  • Disk state, not an in-memory cache, is the source of truth.
  • Resume skips verified done units and respects dependency readiness.
  • Locked atomic writes protect concurrent updates.
  • The CLI refuses live reinitialization, done-state demotion, and false successful finalization.
  • Status-write failure remains non-fatal observability and does not falsely fail delivery.

Honest failure states

  • needs_attention — work stopped with named open units
  • aborted — the run terminated without meeting its completion bar
  • stale_observability — status writes failed and state must be reconstructed from real artifacts
  • refused_transition — the CLI rejected an unsafe lifecycle mutation

▸ enforcement

Know which claims are executable.

Scripts are linked when this skill owns deterministic machinery. The remaining rules are explicit operating contracts and must not be marketed as hooks.

▸ install and invoke

One skill, three honest surfaces.

skills.sh

Available

Universal skill installation, including Claude Code and Codex.

npx skills add https://github.com/ulpi-io/skills-autonomous-engineering --skill checkpoint-resume

Claude Code plugin

Available

Install the full plugin, then invoke /checkpoint-resume or let routing select it from context.

Claude installation →

Codex plugin

Work in progress

A work in progress on the codex-native-plugin branch — build it, start a new session, then invoke $autonomous-engineering:checkpoint-resume.

Codex installation →