prassanna-ravishankar

adhd

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").

durable-jobs

Use when the user asks for durable or recurring background work, work that should survive peer death, retry/cancel/result tracking, spawned-on-demand workers, agent folders, daily briefs, or deciding between repowire jobs and schedule.

Testing & QA Listed

integration-test

Integration test for repowire peer-to-peer messaging. Supports claude-code, opencode, or mixed-agent-type testing with circle boundaries and cross-agent-type communication. Can run all modes in parallel via agent teams.

cleanup

Use when cleaning up peers, sessions, tmux panes, processes, feature worktrees, branches, generated artifacts, or after a delegated lane or PR is complete.

coordination

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.

create-agent

Use when creating, updating, or explaining a standing Repowire agent folder, worker folder, durable-job executor context, or reusable agent-specific AGENTS.md guidance.

create-skill

Use when adding, updating, splitting, or reviewing local orchestrator skills for reusable procedures, including controlled self-improvement of the orchestrator.

delegation

Use when handing work to another peer, deciding whether to spawn or reuse a peer, briefing a lane, asking for a plan before code, or using a second peer for critique or review.

handover

Use when transferring orchestrator responsibility, summarizing current state for a new peer, recovering after a closed session, or preparing takeover notes.

memory

Use when deciding whether to write, read, update, consolidate, or avoid orchestrator memory; distinguishing memory from board status, job state, session history, or project-local agent context.

review-cycle

Use when coordinating PR review, CI triage, second-peer critique, requested-changes loops, merge readiness, or deciding whether implementation needs independent verification.

worktree-isolation

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.