three-shifts

Decomposes high-level tasks into atomic steps and executes them in 15-minute cycles with persistent state.

Updated Feb 18, 2026

Search Tags:#task-decomposition #state-persistence #workflow-management #cycle-execution #shift-automation

Ready to run

npx skills add https://github.com/profbernardoj/travelclaw.org --skill three-shifts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: three-shifts
Source: https://github.com/profbernardoj/travelclaw.org/tree/main/three-shifts
Command: npx skills add https://github.com/profbernardoj/travelclaw.org --skill three-shifts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cyclic, multi-shift workflow planning and execution with persistent state.

Core Features & Use Cases

Plans three daily shifts (6 AM, 2 PM, 10 PM) and decomposes tasks into small, verifiable steps
Executes one step per 15-minute cycle and persists results to workspace files
Uses Claude 4.6 for planning and GLM-5 for execution to balance quality and cost
Recovers gracefully from errors by logging, retrying, and carrying state between cycles
Suitable for long-running automation, memory-heavy workflows, and repeatable ops in distributed teams

Quick Start

Approve the daily shift plan to kick off automated planning, decomposition, and 15-minute cycles.

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 workflows with persistent state between execution cycles?▼

Long-running workflow automation persists state between fixed 15-minute execution cycles to recover gracefully from failures. It decomposes high-level tasks into atomic steps, logging and retrying errors while carrying state forward in workspace files.

What is task decomposition and how does it work for multi-shift cycle execution?▼

Task decomposition for multi-shift cycle execution breaks high-level tasks into small, verifiable atomic steps. It plans three daily shifts at 6 AM, 2 PM, and 10 PM, executing one step per 15-minute cycle and storing results in workspace files.

How do I set up cyclic task execution using Claude for planning and GLM for execution?▼

Cyclic task execution uses Claude 4.6 for planning and GLM-5 for execution to balance quality and cost. You approve the daily shift plan to kick off automated planning, decomposition, and 15-minute execution cycles.

Can I use shift automation for memory-heavy workflows in distributed teams?▼

Shift automation suits memory-heavy workflows and repeatable operations in distributed teams. It plans three daily shifts, executes one step per 15-minute cycle, and persists results to workspace files to ensure state recovery.

Why does multi-shift workflow planning use fixed 15-minute cycles?▼

Multi-shift workflow planning uses fixed 15-minute cycles to execute one atomic step at a time, ensuring verifiable progress. This cycle execution persists state between intervals to recover from errors and carry results forward.

What are the limitations of rule-based shift automation for task execution?▼

Rule-based shift automation operates strictly on fixed 15-minute cycles and three daily shifts, limiting execution to one atomic step per cycle. It requires approving the daily shift plan and depends on workspace files for state persistence.