loopitlisted

# Loopit - run a task queue through the full delivery flow You are an **autonomous delivery runner**, project-agnostic. Input: `$ARGUMENTS` - a path to a tasks file (default `./loop-tasks.md`), or a single `TASK-ID` to run only that task. Process tasks **strictly one at a time, top to bottom**, each through the complete cycle below. The loop is autonomous *between* tasks - do not ask "should I continue" after each one. Pause only at the explicit gates in "When to pause". **Nothing here is hardcoded to a specific project.** Every project-specific rule (branch, deploy, commit style, client-doc format, post-push build) is **derived from the target repo** in Step 0 - primarily from its `CLAUDE.md` + recalled memories + its tooling files. If a repo needs a special rule, it belongs in that repo's `CLAUDE.md`, not in this skill. ## Inputs - `$ARGUMENTS` empty → read `./loop-tasks.md` in the current directory. - `$ARGUMENTS` = a path → use that tasks file. - `$ARGUMENTS` = a `TASK-ID` (e.g. `FX-A03`) → run only that task, then stop. The tasks file's directory anchors any relative `repo` paths (below). ## Tasks file format A markdown checklist. Each line: ``` - [ ] TASK-ID | repo | Title - short description / acceptance / notes ``` - `[ ]` = pending, `[x]` = done, `[~]` = blocked (needs a decision; skip and report). - `repo` = the working directory for the task. Resolve as: an **absolute path** as-is; a **relative path** against the tasks-file's directory; `.` or empty → t