loop-pickup

Resumes multi-phase plans in fresh worktrees by recovering context and claiming unblocked lanes.

1|Updated Nov 25, 2021
One-click install
npx skills add https://github.com/rstagi/dotfile --skill loop-pickup-rstagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-pickup
Source: https://github.com/rstagi/dotfile/tree/main/.claude/skills/loop-pickup
Command: npx skills add https://github.com/rstagi/dotfile --skill loop-pickup-rstagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on multi-phase projects across parallel Conductor worktrees, a fresh chat session has no memory of prior work. This Skill rebuilds working context from the durable plan store so any agent in any worktree can pick up an unblocked lane and start immediately. ## Core Features & Use Cases - Plan Recovery: Resolves the plan from .loop/plan.md, the Loop daemon, or Kestral when linked, always fetching the freshest copy. - Lane Selection & Conflict Check: Parses phases and status markers, recommends unblocked lanes, and detects claims or file conflicts from sibling worktrees before starting. - Phase Claiming & Context Loading: Claims the phase via Kestral or local status markers, creates the suggested branch, and loads only the context the phase needs. - Auto Mode: Supports headless loop-execute runners with deterministic refusals instead of interactive prompts. - Use Case: You open a new Conductor worktree for a parallel lane of a large effort; run this Skill to recover the plan, claim Phase 3 on branch feat/oauth-token-refresh, and get a focused digest of what to build. ## Quick Start Ask the agent to pick up the plan and start the next unblocked lane for your project in this worktree.

Frequently Asked Questions about loop-pickup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a multi-phase plan in a new worktree?

Run loop-pickup in the fresh worktree or chat. It reads .loop/plan.md or fetches the plan from the Loop daemon, shows available lanes with their status, and lets you claim an unblocked phase on its suggested branch.

How does loop-pickup prevent two worktrees from claiming the same phase?

It conflict-checks before claiming: linked plans check Kestral task assignment and in-progress status, while unlinked plans check the plan's status markers and whether the suggested branch already exists in a sibling worktree.

Does loop-pickup require the Kestral MCP server?

Kestral is only needed when the plan is linked, indicated by a kestralWorkContextId in the plan header. Unlinked plans work purely locally against the Loop daemon and .loop/plan.md with no MCP required.

What happens in loop-pickup auto mode?

Auto mode runs headlessly for loop-execute runners with a specified phase. It skips all interactive prompts, verifies branch and repository match, claims via Kestral if linked, and emits a structured REFUSED line with a blocked status.json on any conflict.

What if a phase's suggested branch is missing or non-descriptive?

The Skill derives a descriptive branch name in the form type/imperative-outcome-slug from the phase title, such as feat/oauth-token-refresh, instead of using bare names like phase-3, and offers to fix the plan on the next handoff.