execute-steps

Track and resume step progress for Shield skills within a single phase.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill execute-steps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-steps
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/execute-steps
Command: npx skills add https://github.com/infraspecdev/tesseract --skill execute-steps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents step-by-step Shield workflows from losing state by giving each phase a reliable way to register steps, track progress, and recover interrupted runs.

Core Features & Use Cases

  • Step Skeleton Registration: Defines a fixed set of mandatory and conditional steps for a single skill phase.
  • Progress Tracking: Marks each step as started, completed, or failed so status stays visible during execution.
  • Resume Support: Detects incomplete work and helps a skill continue from the correct step instead of starting over.
  • Use Case: A planning or implementation skill can use it to preserve progress across long operations that may be interrupted mid-run.

Quick Start

Ask this skill to initialize the current phase’s step list and then update each step as it starts, completes, or fails.

Frequently Asked Questions about execute-steps

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

FAQPage Schema
How do I track workflow state and resume an interrupted step execution cleanly?

Workflow state for interrupted step execution is tracked by registering a step skeleton, updating per-step status to started or completed, and resuming from the correct step. This prevents workflows from losing state mid-run and starting over.

What is step skeleton registration for mandatory and conditional phase steps?

Step skeleton registration defines a fixed set of mandatory and conditional steps for a single skill phase. It establishes the expected progress structure before execution begins, ensuring status stays visible and incomplete work is detected for recovery.

How do I recover an interrupted run and continue from the correct step?

Recover an interrupted run by reading the session state to detect incomplete work and failed steps. The workflow resumes from the correct step instead of starting over, using the tracked per-step status to continue cleanly.

Do I need steps_store.py to initialize and manage session state for step tracking?

Yes, steps_store.py is required to initialize, start, complete, fail, read, and clear session state at the project-scoped path. It provides the underlying functions needed to track progress and support interrupted-run recovery.

Can I use progress visibility for step tracking across long operations that may be interrupted?

Progress visibility for step tracking applies to planning or implementation skills running long operations. It marks each step as started, completed, or failed so status stays visible during execution and allows recovery if interrupted.

What are the limitations of single-phase step tracking for workflow state?

Single-phase step tracking applies to workflows within a single skill phase only. It requires steps_store.py for session state management and does not inherently manage multi-phase orchestration or cross-project state persistence.