// Use when cleaning up peers, sessions, tmux panes, processes, feature worktrees, branches, generated artifacts, or after a delegated lane or PR is complete.
| name | cleanup |
| description | Use when cleaning up peers, sessions, tmux panes, processes, feature worktrees, branches, generated artifacts, or after a delegated lane or PR is complete. |
Cleanup has three parts: mesh registration/session, terminal/process, and workspace artifacts. Treat them separately.
Confirm the work is complete, merged or no longer needed, and no peer/reviewer still needs the workspace. Preserve dirty, unmerged, or unpushed user work unless the user explicitly asked for destructive cleanup.
git fetch origin
git status --short
git log @{u}..HEAD
tmux list-windows -t <circle>
git worktree remove <feature-worktree-path>
git worktree prune
git branch -d <feature-branch>
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 transferring orchestrator responsibility, summarizing current state for a new peer, recovering after a closed session, or preparing takeover notes.
Use when coordinating PR review, CI triage, second-peer critique, requested-changes loops, merge readiness, or deciding whether implementation needs independent verification.