Spiral

The methodology for sustaining a multi-week autonomous PR loop without the agent losing context, running out of work prematurely, or accumulating debt.

The agent does not remember the project. The project remembers itself. Every kind of state lives in git-tracked ledger files with rigid templates. The agent's job collapses to: read ledgers, pick the next slice, run the loop, update ledgers. Every iteration returns to the same artifacts and finds them advanced. The shape is not a loop, it is a spiral: forward-while-circling.

When to invoke

• Initialize: at the start of a fresh project, write the canonical scaffold into the current repository.
• Audit: on an existing project, diff the repository against the canonical structure and print a remediation checklist.

Per-slice execution is the job of randroid-loop. Per-task tracking is the job of task-tracking-dots. This skill is the substrate those two run against.

Why this exists: the three case studies

Three multi-week autonomous-loop projects produced three outcomes. The pattern is in docs/case-studies.md. The short version: