Autonomous Development Loop FAQs

Question 1

What pacing modes are available for the loop?

Accepted Answer

The skill supports multiple pacing modes: 'worker' and 'ci' (270s delay), 'plateau' (1200s delay for retries), and 'night' (3600s delay for long-duration background work).

Question 2

Does this skill integrate with project plans?

Accepted Answer

Yes, it is designed to read from Plans.md or named plans in your project manifest to identify, execute, and mark tasks as complete.

Question 3

How can I stop an active autonomous loop?

Accepted Answer

You can use the command '/harness-loop stop' to request a graceful termination of the current runner, or it will stop automatically if it reaches the max-cycle limit or encounters a blocking issue.

Question 4

What is the primary purpose of harness-loop?

Accepted Answer

It automates long-running development tasks by executing them in a continuous, self-governing cycle of planning, working, and reviewing across fresh Claude sessions.

Question 5

How does it maintain context between wake-up cycles?

Accepted Answer

It utilizes ScheduleWakeup to trigger re-entry and employs harness-mem resume packs to restore the necessary state and context at the beginning of every cycle.

Autonomous Development Loop

Key Features

Use Cases

TaskFlow Inbox Triage

Lehrgeld

Agent Skill Creator

Key Features

Use Cases