Codex Run Loop

Coordinate Codex worker threads that turn planned tasks into draft PRs. Use this when the user asks for a coordinator to work through tickets, especially in parallel or with separate worktrees. For one ordinary coding task, code it directly unless the user asks for this loop.

Workflow

1. Select Work

Read the requested tickets, source context, issue tracker context, and repo state. Classify tickets as independent, dependent, conflicting, or unclear. Run independent tickets in parallel, run dependent tickets in waves, sequence conflicting tickets, and stop on unclear acceptance criteria.

For dependent tickets, prefer stacked draft PRs when each ticket remains reviewable on its own. If the tickets are really one feature or heavily overlap, ask whether to use one integration branch and PR.

2. Prepare Worktrees

Inspect git status, current branch, remotes, and existing worktrees. For each unblocked ticket in the current wave, derive a traceable branch name from the ticket ID and short task summary, then create a separate worktree. Default to a sibling root such as ../<repo-name>-worktrees/<branch-name>.

Use git worktree add -b <branch> <path> <base> for new branches. Reuse an existing worktree only when it is for the same branch and clean.

For stacked PRs, base each dependent branch on its predecessor branch. For an integration PR, run the dependent tickets sequentially in one integration worktree.