cc-repete-plugin

Operate a cc-repete autonomous loop well — write a verifiable mission goal, set up the frozen constitution vs. the evolving brief, author lesson cards, read checkpoints, and tune budgets. Use this whenever the user is starting, configuring, resuming, or debugging a repete run (the /repete, /repete-continue, /repete-status, /repete-cancel commands), mentions a "repete loop", an autonomous/self-evolving loop, a ".repete/" directory, a mission goal, loop checkpoints, context-rot pauses, or a lesson library — even if they don't name the plugin explicitly. The single biggest failure mode is a vague mission goal producing a runaway loop, so reach for this skill before the first iteration runs.

Decide whether and how to run an agent in an autonomous loop — repete (single-session re-inject) vs. ralph (fresh process per iteration) vs. a one-shot, plus how to fight context rot with memory layering. Use this whenever the user is weighing "should I loop this", asks about autonomous/agentic loops, iteration harnesses, context rot, a long unattended run, a ralph loop, set-and-forget agents, or how to keep a long agent run from degrading — even if they don't name a specific tool. Reach for this before architecting a loop, so the choice is grounded in how context rot actually behaves rather than vibes.