three-shifts

Coordinate recurring shift execution for long-running AI workflows.

23|5|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/EverClaw/EverClaw --skill three-shifts-everclaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: three-shifts
Source: https://github.com/EverClaw/EverClaw/tree/main/three-shifts
Command: npx skills add https://github.com/EverClaw/EverClaw --skill three-shifts-everclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a long-running workflow into a reliable shift-based execution system, so approved work is planned once, broken into small steps, and completed without losing progress to timeouts or crashes.

Core Features & Use Cases

  • Shift Planning: Creates morning, afternoon, and night plans with priorities, carryover items, and approval-aware task selection.
  • Atomic Cycle Execution: Processes one small step per 15-minute cycle, marking work as complete, blocked, skipped, or in progress.
  • Stateful Handoffs: Persists tasks, context, and results across runs so the next cycle or shift can continue cleanly.
  • Use Case: An operator can approve a daily work queue, let the Skill decompose it into safe steps, and rely on it to keep executing and documenting progress until the shift ends.

Quick Start

Use the three-shifts skill to read the current shift files, decompose the approved work into atomic steps, and update the shift state for the next cycle.

Frequently Asked Questions about three-shifts

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

FAQPage Schema
How do I automate long-running AI workflow execution without losing progress to crashes?▼

Shift cycle execution breaks approved work into small atomic steps processed in 15-minute loops. It requires persistent state files to track task status and uses cron-driven scheduling to complete steps safely without losing progress.

How do I handle task carryover and state handoffs for recurring cron-driven workflows?▼

Stateful handoffs persist tasks, context, and results across runs using persistent state files. The next cycle or shift reads these files to continue cleanly, automatically managing carryover items and approval-aware task selection.

What is the best way to decompose a daily work queue into safe execution steps?▼

Stepwise task decomposition breaks an approved daily work queue into one small step per 15-minute execution loop. Each atomic step is marked as complete, blocked, skipped, or in progress to ensure safe execution.

Do I need persistent state files to run shift planning and execution cycles?▼

Yes, persistent state files are required to store shift plans, carryover items, and execution results. The cron-driven scheduling relies on these files to maintain state across morning, afternoon, and night planning cycles.

How does approval-aware planning work for automated task execution?▼

Approval-aware planning requires an operator to approve a daily work queue before execution begins. The system then decomposes the approved tasks into safe steps and executes them, relying on retry-safe error logging for failures.

Why is my long-running workflow timing out before completing all planned tasks?▼

Workflows timeout when processing too much work in a single run. Shift cycle execution solves this by breaking work into atomic 15-minute cycles with end-of-shift handoff generation, allowing tasks to resume in the next cycle.