takeover

Resume paused work streams from centralized .state/works/ directories and drive them to completion.

4|1|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/alvis/.agents --skill takeover-alvis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: takeover
Source: https://github.com/alvis/.agents/tree/main/plugins/essential/skills/takeover
Command: npx skills add https://github.com/alvis/.agents --skill takeover-alvis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI-assisted work often gets paused mid-stream, and resuming it safely requires reconstructing context, resolving pending decisions, and knowing which checkout owns the code. This Skill reads the centralized work state under the default source tree's .state/works/, settles reviewing streams against landing evidence, and drives one selected stream toward its charter without losing durable facts. ## Core Features & Use Cases - Centralized state resumption: Enumerates every incomplete work stream from state_root/.state/works/, reads each stream's recorded source-checkout Location, and resumes from on-disk state without bootstrap or disposable trees. - Reviewing-stream settlement: Checks coding streams for merged PRs via gh pr view and non-coding streams for explicit acceptance plus promotion receipts before marking them completed. - Risk-appropriate execution: Classifies runnable actions by tier, handing bounded Tier 0/1 work to one implementing owner, adding independent review at Tier 2, and routing Tier 3 work through lead coordination. - Delegated publication: Delegates pull-request creation and monitoring to an executor agent running the change-publication capability, and promotes durable facts to authoritative destinations at completion. - Use Case: You return Monday morning to three paused coding streams across two worktrees. Run takeover to see unblocked streams first, pick one, and have it resumed, implemented, PR'd, and parked at reviewing with all decisions journaled. ## Quick Start Resume my paused work streams and continue the one I select toward completion.

Frequently Asked Questions about takeover

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

FAQPage Schema
How do I resume paused work across multiple Git worktrees?

Run takeover to enumerate every incomplete stream in the centralized .state/works/ directory, which all worktrees share. It reads each stream's recorded Location, lets you select one stream, and switches the working directory to the owning checkout before resuming.

How does takeover handle streams stuck in reviewing phase?

Before offering new work, it settles every reviewing stream by checking landing evidence: merged PRs via gh pr view for coding work, or explicit acceptance plus a promotion receipt for non-coding work. Settled streams become completed; unsettled ones stay reviewing and are excluded from resumption.

What happens when the recorded source anchor differs from the current checkout?

The stream stops and reports the exact revision it assumes, asking you to bring the checkout to that anchor or re-run takeover in a worktree at that revision. The --revalidate flag forces this comparison even when the anchor appears to match.

Does takeover create pull requests itself?

No. The main session never creates, updates, or monitors pull requests. It delegates all PR work to an executor agent running the change-publication capability, then records the resulting PR URLs; non-coding streams produce no pull request.

What are the limitations when resuming another session's work?

A lease left by another owner is never inherited; expired leases must be claimed through the explicit takeover verb, and a live foreign lease stops the stream entirely. Damaged state directories are not repaired inline — the skill recommends running essential:doctor instead.