manager-with-local

Persist manager delegation chains into local breadcrumbs for crash-recoverable operation tracking.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/josephwander-arch/manager --skill manager-with-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manager-with-local
Source: https://github.com/josephwander-arch/manager/tree/main/skills/manager-with-local
Command: npx skills add https://github.com/josephwander-arch/manager --skill manager-with-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manager delegation chains are ephemeral and can be lost when an agent context resets, causing wasted work and difficult handoffs. This Skill prescribes using local breadcrumbs to persist multi-step delegations so teams can resume, audit, and recover long-running or cross-context operations.

Core Features & Use Cases

  • Breadcrumb lifecycle: start a breadcrumb before the first manager call, log each completed step with files_changed, and complete or abort explicitly to avoid orphans.
  • Crash recovery & handoff: persisted step logs let a new session or agent read breadcrumb_status and resume at the correct next step.
  • Failure handling: record failed steps, retry or rollback with explicit logs, and include failure context for safe decisions.
  • Loaf integration: combine manager-level loafs for task DAGs with local breadcrumbs for operation-level progress and audit.
  • Use case: multi-step code refactors, long-running build/test/deploy pipelines, and cross-machine developer handoffs.

Quick Start

Start a local breadcrumb before your first manager delegation, call breadcrumb_step after each completed delegation including files_changed, and finish with breadcrumb_complete so the operation can be resumed or audited later.

Frequently Asked Questions about manager-with-local

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

FAQPage Schema
How do I persist task delegation chains for crash recovery?

Persist task delegation chains for crash recovery by writing local breadcrumbs before each manager call, logging completed steps with files_changed, and explicitly completing or aborting to avoid orphaned operations.

What is local breadcrumb lifecycle management for multi-step task orchestration?

Local breadcrumb lifecycle management for multi-step task orchestration is the process of starting a breadcrumb, logging each completed delegation step with files_changed, and explicitly completing or aborting to ensure auditable, crash-recoverable tracking.

Do I need both manager and local servers installed for delegation tracking?

Yes, you need both manager and local servers installed for delegation tracking. This Skill applies when you have coordinated, multi-step delegations or loaf-driven task groups that may exceed a few minutes and require durable cross-context persistence.

How do I resume a multi-step refactor after an agent context reset?

Resume a multi-step refactor after an agent context reset by reading the persisted breadcrumb status. A new session or agent reads the local breadcrumb logs and resumes the operation at the correct next step with full audit context.

What is the best way to handle rollback and retry patterns in long-running pipelines?

Handle rollback and retry patterns in long-running pipelines by recording failed steps in local breadcrumbs, logging failure context for safe decisions, and executing explicit retry or rollback operations to maintain auditable operation tracking.

When should I not use local breadcrumbs for task orchestration?

You should not use local breadcrumbs for task orchestration if your delegations are short-lived, single-step operations, or if you lack the required manager and local servers, as the breadcrumb lifecycle overhead provides no crash recovery benefit for ephemeral tasks.