harness-looplisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Harness Loop ## Scope Owns driving tracked work through the whole development loop with the `basicly loop` command group over the owned tracker ledger — one unit at a time with `loop run`, or many lanes at once with `loop preflight` + `loop supervise`. The loop is agent-agnostic: the same commands drive it under Claude, Codex, or Copilot — the agent supplies the phase inputs (the work type, the child plan) and does the coding in the worktree; the engine records state, gates, and advances. It is **not** for the mechanics each phase delegates to — those have their own skills: `work-tracker` (create/claim/close records), `worktree-isolation` (isolate a node's build), `conventional-commits` (format the commit), `tool-git` (staging, diffing). This skill sequences them; it does not replace them. ## The tracker is the state — start by reading it The tracker ledger is the single source of truth; the loop keeps no side-state, so it is resumable across restarts and across agents. Whatever happened last session, begin by reconstructing where a track is: ```sh basicly loop status <issue> # phase, worktree binding, gates, checkpoints, rework, ready/blocked ``` That one command also prints the **ranked ready set and the blocked set**, so it is where you pick the next issue as well as where you read the current one's phase. See `work-tracker` for reading a record's own body. ## Tracker