skills.rest
anotherben
anotherbenCOMMUNITY
Explore all skills by this author →
GitHub

conductor-resume

Load fleet state and worker handovers from Obsidian to resume conductor dispatch workflows.

6|Updated Mar 18, 2026
Search Tags:#workflow#dispatch#governance#resume#conductor#handover
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill conductor-resume
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conductor-resume
Source: https://github.com/anotherben/claude-harness/tree/main/skills/conductor-resume
Command: npx skills add https://github.com/anotherben/claude-harness --skill conductor-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resumes a conductor dispatch by loading fleet state and handovers from Obsidian, surfacing completed and failed work, and guiding next-step decisions.

Core Features & Use Cases

  • Load and review fleet state from past dispatches to understand progress.
  • Inspect handovers for each worker and validate decisions or blockers.
  • Present actionable options (verify, redispatch, merge) to drive continued governance.

Quick Start

Run the conductor resume workflow to load the latest fleet state and present available actions.

Frequently Asked Questions about conductor-resume

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

FAQPage Schema
How do I resume a conductor dispatch and review fleet state?▼

You resume a conductor dispatch by loading fleet state and worker handovers from Obsidian, which surfaces completed and failed work to guide next-step decisions like verifying, redispatching, or merging results.

What is a conductor handover and when do I need to inspect it?▼

A conductor handover records worker decisions and blockers from a dispatch session. You need to inspect handovers during post-dispatch recovery to validate completed work and identify failed tasks for redispatching.

Can I use Obsidian to manage workflow governance and dispatch recovery?▼

Yes, this workflow loads fleet state and worker handovers directly from Obsidian to present dispatch outcomes and drive continued governance through deterministic scripting and evidence handling.

What's the best way to handle failed workers after a fleet dispatch?▼

The best way to handle failed workers is to load the fleet state, inspect the handovers to identify blockers, and use the presented redispatch action to reassign the failed tasks across the fleet.

How do I merge results across a fleet after a dispatch session?▼

You merge results across a fleet by running the conductor resume workflow, which loads the completed worker handovers from Obsidian and presents the merge action to consolidate the dispatch outcomes.

Related Skills

Explore More Software Engineering Skills→
NodewarriorNodewarrior
21

spine-init

Create or adopt a Spine Architecture vault with Obsidian structure and config.

Community
Intermediate
robertpellonirobertpelloni
2

finishing-a-development-branch

Validate tests and execute merge, PR, or cleanup workflows for Git branches.

Community
Intermediate
KiloforgeKiloforge
2

kf-conductor

Coordinate multiple Claude Code workers via tmux with automatic dispatch and lifecycle management.

Official
Advanced
anotherbenanotherben
6

fleet-commander

Coordinate multi-task batches across agents with dependency analysis and dynamic model routing.

Community
Advanced