← ClaudeAtlas

implementation-harness-pre-loop-checkinlisted

Use for a read-only GO/NO-GO check of the harness backlog BEFORE starting an unattended loop run — phrases like "is the backlog ready to run", "check before I start the loop", "pre-flight the harness", "/pre-loop-checkin". Reports needs-human blockers, session hygiene (dirty tree / running loop / lock), dependency short-circuits, and per-task definition quality (facets, spec, scope), then a plain GO / NO-GO verdict. Strictly READ-ONLY — it never edits, commits, or pushes anything. Requires the harness scaffolded.
RyanMKrol/claude-skills · ★ 0 · Data & Documents · score 73
Install: claude install-skill RyanMKrol/claude-skills
# Pre-loop check-in (read-only GO/NO-GO) Vet the autonomous build harness (`.harness/scripts/loop.sh`, run via `.harness/scripts/supervise.sh`) **BEFORE** the owner starts an unattended run. This is the pre-run mirror of `/implementation-harness-loop-recover` — but where that command diagnoses AND FIXES state, this one only **looks and reports**. Focus target: `$ARGUMENTS` (a task id narrows checks 1 and 4 to it but still runs the global checks 2 and 3; empty = full sweep). Read this whole file, then run the checks. For the plain "what's ready / blocked / done" status board, `.harness/scripts/postflight.sh` already exists (zero-token). This command adds the pre-run **quality validation + a GO/NO-GO verdict** on top. ## ⚠️ Guardrails (read-only / advisory-ONLY — do not violate) - **You MUST NOT edit `.harness/tracking/TASKS.json`** — not `status`, not `facets`, nothing. Read only. - **You MUST NOT write, commit, or push ANY file.** No worklog entries, no ledger rows, no scratch. This is purely observational. - **You MUST NOT touch the owner overlays** (`tracking/reviews.json`, `human-done.json`, `manual-fail.json`) — only READ them (to see whether a needs-human blocker is about to auto-reconcile). - **No destructive/mutating git** — no `commit`, `push`, `add`, `reset`, `clean`, `restore`, `checkout --`, `rebase`, branch create/delete. `git status`/`log`/`fetch`/`rev-list`/`rev-parse` (read-only) are fine. - If you find something that needs fixing, **report it** — don