Menu
Pair-programming mode protocol for writer/reviewer clone coordination. Load when mode is pair-programming.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | manta-pair-protocol |
| description | Pair-programming mode protocol for writer/reviewer clone coordination. Load when mode is pair-programming. |
| audience | clone |
| version | 0.1.0 |
| related | ["manta-as-clone","manta-daemon-idle","manta-graceful-death","manta-pair-writer","manta-pair-reviewer"] |
Coordination protocol for pair-programming mode. Two daemon clones collaborate: one writes code, the other reviews each commit. The orchestrator mediates via the PairDispatcher state machine with broadcast-based signaling.
After loading this skill, load your role-specific skill: manta-pair-writer (if you are the writer) or manta-pair-reviewer (if you are the reviewer). Your role is specified in your task contract's approach_hint field.
commit_ready, transition to IDLEreview_complete with verdict, transition to IDLEmanta.heartbeat for state transitions, manta.broadcast for coordinationmanta.read_broadcasts for cross-clone signalsmanta-graceful-death between iterations — only at session end# Writer completes implementation:
manta.broadcast({ clone_id: "A", event_type: "commit_ready",
payload: { commit_ref: "abc123", summary: "implement query builder cache",
files_changed: ["src/cache.ts"], iteration: 1 } })
manta.heartbeat({ clone_id: "A", state: "IDLE" })
# Reviewer reviews and responds:
manta.broadcast({ clone_id: "B", event_type: "review_complete",
payload: { verdict: "changes_requested", iteration: 1,
comments: [{ file: "src/cache.ts", line: 42, severity: "correction",
comment: "missing edge case for empty input" }] } })
manta.heartbeat({ clone_id: "B", state: "IDLE" })
# PairDispatcher delivers feedback to writer via work queue.
# Writer applies feedback, re-commits, broadcasts commit_ready again.
# After approval: both clones proceed to graceful death.
Pre-cast self-check for the main agent. Do I actually need clones? Which of the 9 modes? Am I within my subscription's usage/rate limit? Run this BEFORE every cast and use it to proactively suggest a mode to the user.
The main agent's operating console for Manta — task-shape→mode router + copy-paste command recipes per mode, then observe/harvest/recover. Load BEFORE any manta cast / /manta:* / manta_* tool. Be proactive — when a task fits a cast shape, offer it.
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.
Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.
File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.