stopCompany

Pause all Sub AI statuses and set company state to stopped.

Updated May 21, 2026

Search Tags:#ai orchestration #pause #workflow control #company management #system state #task interruption

Ready to run

npx skills add https://github.com/kinetas/harness_engineering --skill stopcompany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stopCompany
Source: https://github.com/kinetas/harness_engineering/tree/main/stopCompany
Command: npx skills add https://github.com/kinetas/harness_engineering --skill stopcompany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It stops all running AI operations when you need an immediate halt, without losing task data.

Core Features & Use Cases

Pauses Sub AI execution: Switches all Sub AI statuses to PAUSED so ongoing work stops right away.
Keeps Boss AI available: Leaves Boss AI active (STANDBY for other Main AIs) so the user can continue issuing commands.
Persists a stopped state: Updates doc/company_state.json to status "stopped" for consistent recovery behavior after a pause.

Quick Start

Invoke /stopCompany to pause all AI operations immediately while preserving the current task data.

Frequently Asked Questions about stopCompany

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

FAQPage Schema

How do I pause all AI workflows for immediate maintenance?▼

To halt all AI operations, the command switches every Sub AI status to PAUSED and updates company_state.json to stopped. This immediately interrupts all active workflows while preserving current task data for later recovery.

Can I issue commands to the Boss AI during a company-wide task interruption?▼

Yes, you can issue commands to the Boss AI during a task interruption. The system switches Sub AI statuses to PAUSED but keeps the Boss AI in STANDBY mode so it remains available to receive your operational commands.

What happens to my task data when I stop AI operations across the company?▼

Stopping AI operations preserves your task data completely. The process updates the system state to stopped and switches active workers to PAUSED, ensuring that no ongoing task information is lost during the controlled workflow interruption.

What files are required to manage system state for pausing AI workers?▼

Managing system state requires reading doc/AI_list.txt to identify active Sub AIs and doc/company_state.json to update the operational status. These files coordinate the workflow control and ensure consistent recovery behavior after pausing.

When should I use a controlled workflow interruption for AI orchestration?▼

Use a controlled workflow interruption during system maintenance, emergency reviews, or when you need an immediate halt to prevent further processing. It safely stops all active AI operations across workers without losing task data.