← ClaudeAtlas

pinboardlisted

Coordinate one pinboard for live status, next-work selection, safe parallel work, worker dispatch and continuation, lifecycle changes, review acceptance, recovery, or long-running continuity. Use when coordinating workers or changing shared work state. Do not implement a worker's assigned attempt; use $pinboard-deliver for that implementation.
valsteen/pinboard · ★ 4 · AI & Automation · score 77
Install: claude install-skill valsteen/pinboard
# Coordinate with the pinboard Coordinate shared work through one project-local ledger while keeping execution isolated by attempt. Any task may apply an atomic project transition. Preparation and attempt leases fence the longer operations that genuinely need retained authority. Use [the coding-agent runtime adapters](references/runtime-adapters.md) for identity, checkout isolation, subagents and reviewers, permission declarations, waiting, and optional messaging. This skill owns the shared decisions in both integrations. ## Confirm broad scope once Before broad autonomous work begins—including repository-wide work or an outcome spanning several principal product, documentation, agent, tooling, packaging, or CI surfaces—give the human one short declarative sentence that names the intended outcome, the main surfaces expected to be read and touched, the approximate magnitude, and any surprising exclusion. State magnitude in terms the human can correct, such as one representative family versus the whole supported repository. This sentence confirms the interpretation; it is not a permission question, an internal plan, or a canonical brief. When the human already authorized immediate execution, continue after the sentence without asking again. In a one-shot client, include the sentence before the next tool call in the same response and keep working; do not end the turn merely to deliver it. Broadness, elapsed time, several workflow stages, or the need for review is not an arc