loop-run

Advance an agent loop one state transition and persist checkpoints.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-run
Source: https://github.com/SollanSystems/loop-engineer/tree/main/skills/loop-run
Command: npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you operate a long-running agent loop without losing state, skipping verification, or pretending a task is finished before the gate proves it.

Core Features & Use Cases

  • Advance the loop one transition at a time from intake through planning, execution, verification, repair, and terminal states.
  • Persist checkpoints, task status, run logs, approvals, and verification evidence so the run can survive compaction and resumption.
  • Use it when resuming an existing run, handling approval pauses, or coordinating bounded repair after a verification failure.

Quick Start

Use the loop-run skill to resume the existing loop workspace, advance exactly one transition, verify the result, and stop only when the next explicit terminal state is reached.

Frequently Asked Questions about loop-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a long-running agent loop after a context compaction without losing task state?

Resuming a long-running agent loop requires persisting checkpoints with state.json, task tracking, and run logs so the execution can recover safely and advance one state transition at a time without losing prior context.

What is state machine task orchestration for agent loops?

State machine task orchestration for agent loops is the process of advancing execution through discrete states like planning, execution, and verification. It enforces independent gates and explicit terminal states to ensure tasks are only marked complete when verification proves it.

How do I handle approval pauses in a long-lived automated task workflow?

Handling approval pauses in an automated task workflow requires a state machine that persists the current checkpoint and halts execution. The workflow resumes from the approval state only after explicit human input is recorded and the next transition is triggered.

Can I use checkpointing to coordinate bounded repair after a verification failure?

Yes, checkpointing can coordinate bounded repair after a verification failure by transitioning the state machine to a repair state. It persists the failure evidence and task status, allowing the agent loop to attempt fixes without re-planning the entire run.

Does loop-run require a specific contract for state tracking and verification gates?

Yes, operating this agent loop requires a skill-backed contract with state.json, task tracking, independent verification gates, and explicit seven-state termination. Without this structured contract, the loop cannot persist checkpoints or safely handle terminal states.

When should I not use a single-step state transition approach for task orchestration?

You should not use a single-step state transition approach when your workflow requires dynamic re-planning or lacks independent verification gates. This method is designed for bounded execution, repair, and approval pauses without re-planning the overall task strategy.