Reconcile worktree progress against a multi-phase plan and repush it to the Loop daemon and Kestral.
npx skills add https://github.com/rstagi/dotfile --skill loop-handoff-rstagi
Please help me install this Agent Skill. Skill: loop-handoff Source: https://github.com/rstagi/dotfile/tree/main/.claude/skills/loop-handoff Command: npx skills add https://github.com/rstagi/dotfile --skill loop-handoff-rstagi
[status: …] markers, the Status/Last updated lines, and appends a Progress log entry. - Multi-target repush: Writes the updated plan to .loop/plan.md, pushes it to the Loop daemon via loop-plan.sh push, and—when the plan is linked—syncs the Kestral plan document, task statuses, and progress comments. - Auto mode for loop-execute: Supports --auto invocations from runner and orchestrator contexts with no confirmation gates, strict plan-writer ownership rules, and mandatory secret redaction. - Use Case: After finishing a phase in a Claude Code worktree, run the handoff so a Codex session in another worktree can run /loop-pickup and continue exactly where you left off. ## Quick Start Ask the assistant to hand off this session's work by reconciling progress against the loop plan and repushing it so a fresh chat can pick it up.High-intent search queries and answers about installing and using this skill.
Run the loop-handoff workflow: it reconciles git progress against the plan's phases, updates status markers and the progress log, repushes the plan to the Loop daemon and Kestral, then prints a resume pointer. The next session continues with /loop-pickup.
When the plan is linked (its header carries kestral coordinates), the skill updates the Kestral plan document via update_document and delegates task status changes, progress comments, and PR linking to the kestral-sync skill. Unlinked plans only update the daemon and local files.
Yes. The handoff state lives in the Loop daemon, .loop/plan.md, and Kestral rather than in the conversation, so any host can resume it. A Codex worktree runs $loop-pickup with the planId or project to continue exactly where the previous session stopped.
In interactive mode the skill falls back to a lighter handoff: it syncs the task via kestral-sync when linked, or invokes the generic handoff skill for a narrative summary. In auto mode there is no fallback—it returns REFUSED with a reason instead.
The runner (status:in-progress) only writes events and notes via loop-plan.sh note or post_progress_comment, never pushing the plan. The orchestrator (status:done|blocked) performs the full handoff after merge, including loop-plan.sh push and Kestral document and task updates.
microsoftCreate evidence-based implementation plans and phase details from research and user decisions.
DagimAlemayehuuResumes and recovers Agentic Engineering projects from durable repository state.
Kestral-TeamSync coding session progress, task statuses, and PR links with Kestral.
mwayGenerate standalone implementation plans with phases, tasks, and acceptance criteria.