autospec-stop

Write a stop sentinel to halt an autospec monitor gracefully or at the next step boundary.

3|1|Updated Apr 29, 2026

Search Tags:#workflow interruption #GitHub issues #pause and resume #autospec #monitor control #sentinel flag

Ready to run

npx skills add https://github.com/berlinguyinca/autospec --skill autospec-stop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autospec-stop
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-stop
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-stop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autospec monitors need a controlled way to halt execution without corrupting the workflow or leaving you unsure what state the system is in.

Core Features & Use Cases

Graceful halt: Writes a sentinel so the monitor exits after finishing the current issue, preserving workflow integrity.
Immediate halt: Aborts at the next step boundary by writing a different sentinel mode and leaving a paused state for later recovery.
Operational recovery: Supports status reporting and resuming by restoring paused issues and cleaning up the stop sentinel.
Use Case: You start an autospec run, realize requirements changed, and need to stop now while keeping a consistent queue and resuming later without redoing work.

Quick Start

Ask your agent to stop the running autospec monitor immediately: autospec-stop --immediate

Frequently Asked Questions about autospec-stop

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

FAQPage Schema

How do I safely pause a running autospec monitor without corrupting the workflow?▼

To safely pause an autospec monitor, issue a graceful halt to write a stop sentinel that lets the monitor exit after finishing the current issue, preserving workflow integrity and queue consistency.

What is the difference between a graceful halt and an immediate halt in autospec?▼

A graceful halt exits the autospec monitor after the current issue completes, while an immediate halt aborts execution at the next step boundary, leaving a paused state for later recovery without manual queue surgery.

How do I resume an autospec monitor after stopping it?▼

You resume a stopped autospec monitor by using the resume flag, which restores paused issues, cleans up the stop sentinel, and safely routes execution back across the harness without redoing completed work.

Can I check the status of a paused autospec monitor before resuming?▼

Yes, you can check the status of a paused autospec monitor by passing the status flag to the autospec-stop helper script, which reports the current execution state and sentinel mode for operational recovery.

When should I use an immediate halt instead of a graceful stop for my monitor workflow?▼

Use an immediate halt when requirements change mid-run and you must stop the autospec monitor now, accepting a paused state at the next step boundary to avoid redoing completed work later.