Hyperplan (Adversarial Multi-Agent Planning)
Spins up five mutually hostile agents for three rounds of cross-critique, then turns only the surviving insights into an executable plan.
What it does
hyperplan replaces consensus-style planning with intellectual combat. The orchestrator becomes the Lead of a five-member adversarial team, and each member ruthlessly attacks the others' findings.
- skeptic — pragmatist who attacks over-engineering, scope creep, premature abstraction
- validator — integration tester hunting edge cases, blast radius, failure modes
- researcher — evidence enforcer demanding file:line citations and doc URLs
- architect — exposes hidden coupling, leaky abstractions, architectural debt
- creative — forces at least three alternative framings before anything is accepted
Seven phases: spawn the team → Round 1 independent findings → Round 2 cross-attack → Round 3 defend/refine/concede → Lead distills only survivors into hard constraints, decisions, risks & mitigations, and open questions → mandatory handoff to a planner task running ulw-plan for executable plan formalization → team cleanup. The Lead writing the plan itself is explicitly listed as an anti-pattern.
Who it's for
- Engineers about to commit to expensive work: big refactors, migrations, new architecture
- Tech leads who know solo planning leaves optimistic assumptions and blind spots
- Users already on omo-senpi (oh-my-openagent) with the lead team tools and the
ulw-planskill - Not for vanilla Claude Code users or quick one-off tasks — it's deliberately heavyweight.
Examples
- "hyperplan: move the payments module from Stripe to an in-house PSP abstraction" → researcher pins every call site with file:line, validator enumerates webhook/refund failure modes, skeptic challenges whether the abstraction is needed today; only battle-tested constraints reach the plan.
- "adversarial plan: split the monolith into three services" → creative forces the "just harden module boundaries" alternative, architect surfaces hidden coupling, and unresolved contention becomes a user-input gate in the final plan.
- "hpp redesign the onboarding flow" → findings conceded in Round 3 are dropped entirely; survivors become sequenced tasks with explicit success criteria.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the packages/omo-senpi/skills/hyperplan folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/code-yeongyu-hyperplan-2/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/code-yeongyu/oh-my-openagent.git && mkdir -p ~/.claude/skills && cp -r oh-my-openagent/packages/omo-senpi/skills/hyperplan ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Note upfront: this skill is built for the omo-senpi (oh-my-openagent) runtime — it needs the lead team tools (
team_create,task_send,team_delete) and theulw-planskill. - Open a terminal and clone the repo:
git clone https://github.com/code-yeongyu/oh-my-openagent.git - Copy the skill folder:
mkdir -p ~/.claude/skills && cp -r oh-my-openagent/packages/omo-senpi/skills/hyperplan ~/.claude/skills/ - If you run omo-senpi, restart senpi without the
--no-omo-taskflag so the task component stays enabled. - Verify the
ulw-planskill is also installed (same skills directory in the repo). Without it, the mandatory Phase 6 handoff will fail. - Restart your session and, from the top-level (lead) session, ask something like
hyperplan a plan for refactoring the payments module. You should see "HYPERPLAN MODE ENABLED!". - Expect real cost: five agents across three rounds burns tokens and time. Reserve it for high-stakes planning, and confirm the team is disbanded at the end.