// Use when transferring orchestrator responsibility, summarizing current state for a new peer, recovering after a closed session, or preparing takeover notes.
| name | handover |
| description | Use when transferring orchestrator responsibility, summarizing current state for a new peer, recovering after a closed session, or preparing takeover notes. |
Use handover when continuity matters more than chat transcript detail.
Capture:
Prefer links to durable surfaces over pasted logs: job IDs, ask IDs, branch names, issue IDs, and file paths.
Before acting, verify live state:
repowire peer list
repowire jobs list
git status --short --branch
Assume handover notes can be stale. Reconcile them against the repo, jobs, and active peers before dispatching new work.
Parallel divergent ideation via mesh fan-out. Spawns N frame-shifted peers, scores results, deepens top survivors. Use on open-ended design choices, fuzzy bugs, naming, API surfaces, or explicit /adhd invocation. Skip for syntax, lookups, or closed prompts ("quick", "standard", "canonical").
Use when orchestrating complex or multi-lane work, decomposing tasks across peers, choosing status/board surfaces, running mesh roundups, or keeping high-level progress visible.
Use when creating, updating, or explaining a standing Repowire agent folder, worker folder, durable-job executor context, or reusable agent-specific AGENTS.md guidance.
Use when adding, updating, splitting, or reviewing local orchestrator skills for reusable procedures, including controlled self-improvement of the orchestrator.
Use when coordinating PR review, CI triage, second-peer critique, requested-changes loops, merge readiness, or deciding whether implementation needs independent verification.
Use when splitting work across peers, creating or selecting feature worktrees, preventing overlapping edits, or deciding whether to reroute implementation out of the main worktree.