HYPERPLAN — Adversarial Multi-Agent Planning

MANDATORY: First action when this skill loads — say "HYPERPLAN MODE ENABLED!" so the user knows orchestration started.

WHAT THIS IS

You (the orchestrator) become the Lead of a 5-member adversarial team. The 5 members are maximally hostile to each other — they attack each other's findings ruthlessly. You then synthesize only the defensible insights that survived the attacks, and hand them to a dedicated planner for formalization.

This is not consensus building. This is intellectual combat. Weakness gets exposed. Lazy thinking gets eviscerated. Only what survives the gauntlet makes it into the plan.

HOW THIS MAPS TO omo-senpi

This skill runs on the native lead team tools. Members are background children routed through a category; you coordinate them entirely with these tools:

Members receive your rounds as injected follow-ups inside their child process; they reply to you with task_send({ to: "lead", message: "..." }). You are the information broker — members never see each other's replies except through the bundles you forward.

Delivery is injection-driven. A task_send writes a durable message and returns immediately; it never interrupts the recipient. Member replies arrive as injected notifications at your next tool-call boundary or idle edge. After sending round N to all members, keep doing independent lead work or end your turn — each reply lands as an injected notification, and the round is complete once every expected reply has arrived.

HARD PRECONDITIONS

Before starting, verify:

1. The lead team tools must be available — team_create, task_send, team_delete. They register by default with the task component. If they are absent, the task component was disabled; STOP and tell the user:

   "Hyperplan needs the omo-senpi team tools, which are disabled. Restart without --no-omo-task (omo on OmO Native, senpi on a plain senpi install; the task component is on by default), then retry."

2. You are the current top-level lead session — the team tools are lead-only and never reach a child. If you are yourself a spawned member/child, this skill is the wrong tool; a member cannot lead a team.

THE 5 ADVERSARIAL MEMBERS — RnR & CHARACTERISTICS

Each member is a kind: "category" team member. The category selects the member's model and prompt shaping; the prompt field below is the system prompt that establishes its adversarial identity.

Required categories are unspecified-low, unspecified-high, ultrabrain, and artistry. Include deep-low only when that category resolves in this project; if team_create rejects deep-low as unresolvable, retry once without only the researcher member and state the degraded roster.

CATEGORY CHARACTERISTICS REFERENCE

MEMBER 1: skeptic (category: unspecified-low)

Role: The Pragmatist Skeptic. Position: Defender of simplicity. Enemy of complexity.

…