autonomous

Enforce stateful task tracking and verified stop conditions for autonomous coding sessions.

75|18|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/JKHeadley/instar --skill autonomous-jkheadley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous
Source: https://github.com/JKHeadley/instar/tree/main/.claude/skills/autonomous
Command: npx skills add https://github.com/JKHeadley/instar --skill autonomous-jkheadley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, python3, openssl, tmux, claude, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents autonomous development sessions from stopping too early, losing state, or drifting away from the original goal. It gives the agent a structured way to keep working until the real completion criteria are met.

Core Features & Use Cases

  • Structured autonomous runs: Creates a bounded session with a goal, duration, task list, and completion promise or completion condition.
  • Stateful enforcement: Uses a stop hook and per-topic state files to keep the session alive, track progress, and preserve ownership across restarts.
  • Progress and recovery: Sends periodic progress reports, handles emergency stops, and supports resumable long-running work without silent exits.

Quick Start

Ask the autonomous skill to start a bounded development run for your goal with a task list, a completion condition, and a report topic so it can manage progress and stopping criteria for you.

Frequently Asked Questions about autonomous

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

FAQPage Schema
How do I keep autonomous coding sessions from stopping before the task is complete?

To stop autonomous coding sessions from exiting early, enforce stateful task tracking with verified stop conditions. This approach uses per-topic state files and a stop hook to ensure the session remains active until genuine completion criteria are met.

What is a stop hook and how does it manage session state for long-running workflows?

A stop hook manages session state by intercepting exit signals and validating them against stored completion conditions. It prevents silent exits in long-running workflows by checking state files to determine if the autonomous task is genuinely complete or must resume.

How do I start a bounded development run with progress reporting and recovery?

Start a bounded development run by providing a goal, task list, duration, and completion condition. The session registers a report topic to send periodic progress updates and uses state files to manage resumable ownership across restarts.

Do I need tmux and python3 to run autonomous sessions with restart recovery?

Yes, autonomous sessions with restart recovery require tmux, python3, jq, curl, openssl, and claude. These dependencies support state file management, progress reporting, and the execution of setup and hook scripts for bounded development workflows.

Can I resume an autonomous development workflow if the terminal disconnects?

Yes, you can resume an autonomous development workflow after a disconnect. The skill supports resumable long-running work by preserving ownership and session state in files, allowing the task to recover and continue towards its completion condition across restarts.

When should I not use bounded execution for autonomous coding tasks?

Avoid bounded execution for simple, interactive coding tasks that require immediate human feedback or lack clear completion criteria. It is designed for long-running, stateful development workflows needing emergency-stop handling and verified completion conditions.