loop-project

name	loop-project
description	Orchestrate a multi-stage engineering project through dynamically grouped or stacked Codex tasks, branches, pull requests, independent reviews, remediation cycles, and merge. Use when one goal needs multiple PRs or when the user wants a project carried autonomously from plan to merged changes.

Loop Project

Turn one engineering goal into a dependency-aware PR graph and carry it to merge.

Workflow

1. Read repository instructions, confirm GitHub access, resolve the default branch, preserve unrelated changes, and discover canonical checks.
2. Split work by independently reviewable outcome. Group coupled small changes; separate risky or independently shippable work. Mark parallel, sequential, and stacked dependencies.
3. Show a ledger with scope, dependency, branch, verifier, state, and attempt count.
4. Create one user-visible Codex task per ready unit in an isolated worktree. Require a codex/ branch, behavioral verification where possible, repository checks, commit, push, and ready PR.
5. Reconcile every report with live GitHub state. When a PR head first appears or changes, create a fresh independent review task with the acceptance criteria, diff, and verification evidence.
6. Create a fresh remediation task for active valid findings. Re-review the new head. Stop after three unsuccessful cycles or an earlier ambiguous/destructive blocker.
7. Treat a PR as clean only when required checks pass, independent review has no actionable findings, GitHub has no unresolved thread or active change request, the diff is in scope, and the PR is mergeable.
8. Squash-merge clean PRs in dependency order and delete remote branches. Update or retarget dependent work against the merged base, then rerun checks and review.
9. Finish with task ids, branches, PRs, checks, review cycles, merge commits, and blockers.

Never let an implementation task approve its own work. Never merge silence as approval.