loom-branch-finishlisted

# loom-branch-finish Branch finish is a Git integration and cleanup playbook. It verifies the work, detects whether the workspace is normal, worktree-based, or harness-managed, presents bounded finish options, and records the chosen disposition in Loom records. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-tickets`, `loom-evidence`, `loom-audit`, `loom-retrospective`, `loom-knowledge`, and optionally `loom-shipping-and-launch`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It does not replace ticket acceptance, PR review, release readiness, or operator approval for destructive cleanup. ## Use This Playbook When Use this playbook when: - implementation work on a branch or isolated workspace appears complete - all planned tickets or ticket-defined worker scopes for a branch have returned - the operator needs a clear merge, PR, keep, or discard choice - a worktree may need cleanup after local integration - branch provenance and ticket closure need to agree Skip it when the work is still active, evidence is missing, audit is unresolved, or the next move is release rollout rather than branch disposition. ## Route Use this route: ```text verify -> detect -> summarize -> present -> execute choice -> record -> cleanup ``` ## Verify Before presenting finish options, check that the branch is actually finishable. Confirm: - ticket acceptance i