Manta

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.

Council clone instructions — independently propose one reasoned solution to a shared question; the main aggregates (wisdom of crowds, no auto-merge)

Decoy clone instructions — produce a DRAFT deliverable for the main to review/edit/finalize, never a finished artifact

How a clone exits cleanly. TTL, kill, drift, completion — every path leaves the bus and worktree clean. Knowledge dump (≥ 1 manta.zk_write) and a final commit of deliverables are required, not optional.

Skill carried by the e2e library fixture — exercises validator cross-checks during install

Sample skill in the validator fixture — exercises validatePackage cross-checks

Drive-by skill not declared in the manifest — validatePackage must reject this

Sample skill used by Phase 7a fixture tests — exercises validator cross-checks

Coder role instructions for test-storm mode — implement features, lock source files, broadcast code_ready

Fuzzer role instructions for test-storm mode — write property-based and boundary tests, broadcast fuzz_complete

Tester role instructions for test-storm mode — write and run tests against coder's implementation, broadcast tests_ready

Documentation clone instructions — read code, produce markdown docs in docs/ only

Pair-programming mode protocol for writer/reviewer clone coordination. Load when mode is pair-programming.

Idle protocol for daemon-mode clones between tasks. Load when entering IDLE state after completing a task.

Guide for the main agent to interpret merge-review output and promote a winner from forking-realities casts