メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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").
Get an independent implementation plan from a DIFFERENT AI agent over the repowire mesh before you build (e.g. have Gemini or Codex draft an approach for Claude to critique). Use when you want a second perspective on how to approach a task.
Get a code/PR/plan review from a DIFFERENT AI agent over the repowire mesh (e.g. have Codex review Claude's work). Use when you want an independent second opinion from another backend before merging or committing.
Hand a task to another AI agent peer over the repowire mesh — reuse an existing peer on the chosen backend, or spawn one if none exists. Use when you want to offload work to a specific agent (e.g. delegate a refactor to a Codex peer) and track it to completion.
Install or update repowire and its skill pack from inside an agent session — ensure the repowire CLI/hooks are set up, install the skills, and verify the mesh works. Use on a fresh machine or to refresh skills to the latest.
Reference for how to use the repowire mesh — ask/ack vs notify, broadcast, peer discovery, spawning, and cross-agent workflows. Use when you need to coordinate with other AI agents over repowire and want the right primitive for the job.
| name | delegation |
| description | 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. |
Use this when giving work to a peer.
Reuse a peer when the work continues its existing context in the same worktree. Spawn fresh for independent review, decoupled concerns, cross-model critique, or when the current peer's context is too long.
One worktree per concern. Do not put two implementation peers on overlapping files in the same worktree.
Calibrate brief depth to the cost of getting it wrong.
Always include what success looks like and how the peer should report back.
Ask for a plan before code when a wrong approach would cost more than about 30 minutes to unwind. For architectural-but-bounded plans, use a different-model peer to critique before implementation.
Critique brief: include the proposed plan, files to inspect, risks to probe, and ask for skeptical-but-fair feedback with citations. Relay the critique back to the implementing peer and ask them to absorb or push back with reasoning.
Use a different peer for review when stakes warrant. CI green is not feature verification; smoke the actual behavior for UI, API, or workflow changes.
