What problem does it solve? Working a repository issue end-to-end involves many failure-prone steps: reimplementing already-shipped work, trusting unverified "done" claims, skipping real test gates, and letting implementation permission slide into unauthorized merges or closures. This Skill automates a six-phase contract that prevents each of those failures structurally. ## Core Features & Use Cases - Six-phase orchestration: Orient, discover & qualify, deduplicate, bound & execute, verify, and close out — each phase delegated to a named Bindle-native skill or helper script. - Deduplication before claiming: Runs bin/issue-dedup-scan.sh and reads its exit code (0/3/4/64) to distinguish not-started, evidence-found, and uncertain states before any repository mutation. - Two-authority invariant: Enforces that implementation permission never implies push, PR, comment, close, merge, or release authority — each external mutation requires its own explicit grant. - Workspace isolation: Creates an objective worktree from a fresh origin/main SHA via bin/objective-worktree.sh before any mutating pass, leaving the primary checkout untouched. - Use Case: You run gh issue view 42, decide to work it, and invoke this Skill — it dedups against prior work, isolates a worktree, bounds the scope, runs the repo's real verification gates, and stops at an authority-gated disposition decision instead of auto-closing the issue. ## Quick Start Use the issue-work-loop skill to pick up GitHub issue number 42 in this repository and work it through verification to an honest close-out.
