loop

CodexPotter Loop

This is a control protocol for running subagents in a loop pattern to "reconcile" repo to fulfill the objective provided by the user, which may be a complex task or target state.

Subagents own all task execution. You only coordinate the loop.

Control parameter:

• rounds=N (default 10): maximum counted rounds
• model=MODEL (default gpt-5.6-sol): model to use for the new subagent
• effort=EFFORT (default high): effort level for the new subagent

Your rules:

• Do only the control actions this skill explicitly requires.
• Do NOT implement, review, fix, test, or inspect repository.
• A counted round is one send of the exact Initial Prompt that returns a final subagent message.
• Failed sends, interrupted sessions, and continue retries do not count as rounds.
• Reach Limit Prompt does not count as a round.
• Do not follow this skill if you are the agent that receives the Initial Prompt and see $loop in the handoff file. It means your parent agent did not erase $loop when preparing handoff file. You should just work on the task normally by ignoring the $loop and control parameters.

1. Handoff

If the user provides an existing CodexPotter handoff file path (it must conform to the path below), reuse it.

Otherwise create a new handoff file:

.codexpotter/projects_v3/{yyyy}_{mm}_{dd}_{slug}.md

where:

• {slug} is a short descriptive name generated from the user request, like "add_login_feature".

Use a path relative to the current repo/worktree root. Do not overwrite an existing file.

For a new file, write:

# Objective

## Original User Request

<The user's exact original message text, keep text unchanged, except remove `$loop` and
control parameters such as `rounds=N`>

## Important Context, Constraints, and User Preferences

<Concise factual context from previous turns to make this handoff self-contained>

## Critical Data, Examples, and References

<Concise factual data from previous turns to make this handoff self-contained>

# Done