implementation-harness-fix-scope-gapslisted

Internal fix-side companion to `implementation-harness-pre-loop-checkin`'s check (e) — invoke this when a pre-loop-checkin report (or the owner directly) flags scope-authoring WARNs from `check-task-scope.sh` and wants them triaged. Not meant to be run blind/standalone without a reason — it's the follow-up step after warnings are already known. Fans out one cheap-model subagent per WARN to independently judge real-gap vs false-positive against the spec's own prose, auto-applies confident real gaps to that task's `scope` array, and asks the owner only about genuinely ambiguous cases. This MUTATES `.harness/tracking/TASKS.json` (scope arrays only) and pushes to main. Requires the harness scaffolded.
RyanMKrol/claude-skills · ★ 0 · AI & Automation · score 76

Install: claude install-skill RyanMKrol/claude-skills

# Triage and fix scope-authoring gaps `check-task-scope.sh` is a heuristic, false-positive-tolerant linter (see its own header) — it flags every backtick-quoted file-like mention in a task's spec that isn't in that task's declared `scope`, but it can't tell "the spec means to edit this" from "the spec mentions this for context only." Your job: run it, have a subagent independently judge EACH warning against the spec's own prose, auto-fix the confident real gaps, and only bother the owner with what's genuinely ambiguous. Focus target: `$ARGUMENTS` (a task id narrows the sweep to it; empty = every warning `check-task-scope.sh` finds). Read this whole file, then execute in order. This is the fix-side companion to `/implementation-harness-pre-loop-checkin`'s read-only check (e) — that command only ever reports raw warnings; this one is where they get resolved. ## ⚠️ Guardrails (do not violate) - **The loop MUST NOT be running.** This skill mutates `.harness/tracking/TASKS.json` — exactly what the loop reads and writes. If a `loop.sh`/`supervise.sh` process is alive, or the repo lock is held by a live PID, STOP and tell the owner; do not proceed. - **Scope only.** Never touch `status`, `facets`, `dependsOn`, or any other task field — the only mutation this skill ever makes is appending a path to a task's `scope` array. - **Never invent a scope entry the judge didn't actually recommend.** The subagent fan-out is the source of truth for what gets added; don't add anythin