harness-looplisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Harness Loop ## Scope Owns driving one tracked unit of work through the whole development loop with the `basicly loop` command group over the `br` (beads) tracker. 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: `tool-br` (create/claim/close issues), `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 `br` 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 ``` Pick the next actionable issue with `br ready` / `br scheduler --json`; `basicly loop status` then tells you which phase it is parked in and what it is waiting on. ## Tracker state is zero-touch — the engine commits it, you never do One tracker, everywhere: a loop-provisioned worktree shares the base checkout's `.beads` via br's git-