Slop Fix Batch

Start a batch only on an explicit human $slop-fix-batch (T3 Chat) or /slop-fix-batch (Claude Code) invocation with issue-selection conditions. Loading, editing, testing or planning this skill does not start a batch. Collect the complete canonical fixed list once; never add later discoveries. $slop-fix-issue publishes separately and is not a batch worker. Never create implementation or repair sidebar chats.

The invocation authorizes scoped investigation/implementation, evidence-backed closure of already-resolved issues, verified stacked publication, and conditional management/merging of this batch's ready stacks. The objective is verified merging, not PR creation or merge-request acceptance. Before each new assignment at a safe boundary, process due ready-stack gates, merges and result verification. When selecting a stack for merging, choose the stack with the most currently mergeable PRs first; use existing priorities only to break ties. Count only the merge range allowed by the existing gates, as defined in scheduling. External CI/review waits permit independent construction.

The same invocation authorizes investigation and repair of interactions between batch changes and post-merge regressions caused by this batch, including corrective PR publication and merging under the existing gates. Follow target-branch CI recovery without asking whether to repair, pause affected merges, or choose the future merge strategy again. Preserve parallel standalone auto-merge and the existing multi-PR stack policy. Keep the fixed issue list unchanged; track corrective PRs as recovery work. Request human input only for a concrete missing authority, access requirement, or decision that the existing scope cannot resolve.

Keep management in this coordinator chat through construction, repair and verified completion. Do not create automations, heartbeat jobs or background polling processes. Use interruptible waits of at most 30 seconds only when no independent work is eligible; honor refresh deadlines and shared cooldowns. Recover the same ledger and reconcile owners/effects after interruption.

Read only the current procedure

Read a reference once, then reuse it unless its contents change. Locate headings with rg and read the relevant sections instead of loading every reference or dependency. All roles use validation, runtime tools' common rules plus the recorded runtime section, and worker-prompts' settings/context, assignment verification, and shared API policy.