Run any Skill in Manus with one click

cross-agent-plan

Stars209

Forks33

UpdatedMay 31, 2026 at 22:55

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

prassanna-ravishankar

prassanna-ravishankar/repowire

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

name	cross-agent-plan
description	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.

Cross-agent plan

Ask a peer running a different agent backend to draft (or critique) a plan, so the planning perspective is genuinely independent.

Resolve the planner backend

Explicit argument — if the user named a backend, use it.
Configured default — else:
```
repowire config get skills.default_planner_backend
```
(Empty output means unset.)
Safe fallback — else pick an online peer on a backend different from yours, or ask the user. Never default to your own backend; never hardcode one.

Discover peers/backends: list_peers() (MCP) or repowire peer list (CLI).

Run the planning round

Find (or, with the user's go-ahead, spawn — see delegate) a peer on the chosen backend.
Send the task + constraints and ask for a concrete step-by-step plan.
- MCP: ask(peer_name, "Draft an implementation plan for: <task + constraints>")
- Tracked ask is MCP-only (no CLI lifecycle equivalent — repowire peer ask is a synchronous test utility, not this).
ask returns a correlation_id; the peer replies via ack(corr_id, <plan>).
Critique/merge the returned plan with your own; chain follow-ups with ask(reply_to=corr_id, ...).

Keep the brief tight — state the goal, the constraints, and what a good plan must cover, so the cross-agent plan is comparable to your own.

More from this repository

same repository

adhd

prassanna-ravishankar/repowire

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

2026-06-01209

cross-agent-review

prassanna-ravishankar/repowire

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.

2026-05-31209

delegate

prassanna-ravishankar/repowire

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.

2026-05-31209

repowire-install

prassanna-ravishankar/repowire

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.

2026-05-31209

repowire-patterns

prassanna-ravishankar/repowire

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.

2026-05-31209

coordination

prassanna-ravishankar/repowire

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.

2026-05-26209

name	cross-agent-plan
description	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.

Cross-agent plan

Ask a peer running a different agent backend to draft (or critique) a plan, so the planning perspective is genuinely independent.

Resolve the planner backend

Explicit argument — if the user named a backend, use it.
Configured default — else:
```
repowire config get skills.default_planner_backend
```
(Empty output means unset.)
Safe fallback — else pick an online peer on a backend different from yours, or ask the user. Never default to your own backend; never hardcode one.

Discover peers/backends: list_peers() (MCP) or repowire peer list (CLI).

Run the planning round

Find (or, with the user's go-ahead, spawn — see delegate) a peer on the chosen backend.
Send the task + constraints and ask for a concrete step-by-step plan.
- MCP: ask(peer_name, "Draft an implementation plan for: <task + constraints>")
- Tracked ask is MCP-only (no CLI lifecycle equivalent — repowire peer ask is a synchronous test utility, not this).
ask returns a correlation_id; the peer replies via ack(corr_id, <plan>).
Critique/merge the returned plan with your own; chain follow-ups with ask(reply_to=corr_id, ...).

Keep the brief tight — state the goal, the constraints, and what a good plan must cover, so the cross-agent plan is comparable to your own.