What problem does it solve? When multiple people or AI agents work on the same release from different machines, two actors can unknowingly start the same component. This Skill prevents duplicate work by claiming the component in the shared Marshall store — an exclusive, cross-machine lock — before any branch is created. ## Core Features & Use Cases - Exclusive component claiming: Calls claim_component to take the cross-machine lock, with hard stops on claim_conflict (someone else holds it) and not_startable (blockers unmet or graph unverified). - Lease keepalive and recovery: Heartbeats the claim after each meaningful chunk of work, and recovers a lost claim id after context compaction via my_claims instead of re-claiming. - Work-state transitions: Marks components in_progress after claiming and merged when PRs land, including a batch set_component_states call for landing a whole wave at once. - Use Case: An agent is asked to start work on issue #142. It confirms the component is startable, claims it in the Marshall store, creates the branch feat/pay-142-retry-logic, heartbeats the claim during a long test run, and marks the component merged when the PR lands so dependent components unblock. ## Quick Start Start work on the payments retry component by claiming it in the Marshall store and creating its topic branch.
