Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/hyperplan
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization.
Passed 14 of 23 test cases with the skill, and 6 of 23 without it.
and 6 more in the full report
9 fixed5 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
When configuring the member parameters for an API gateway redesign debate, which category is mapped to the architect role?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns category ultrabrain to the architect member. | Missed | Passed |
The instructions your model reads when the skill loads.
MANDATORY: First action when this skill loads — say "HYPERPLAN MODE ENABLED!" so the user knows orchestration started.
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.
This skill runs on the native lead team tools. Members are background children routed through a category; you coordinate them entirely with these tools:
| Purpose | Tool | Key arguments |
|---|---|---|
| Spawn the team once | team_create | inline_spec: { name, description, members: [...] } → returns team_run_id |
| Send a round task to a member | task_send | to: "<member>", team_run_id, message, optional summary |
| Collect member replies | injected notifications | replies auto-inject as they arrive — keep working or end your turn |
| Hand off to the planner | task | category XOR subagent_type, load_skills: ["ulw-plan"], run_in_background: false |
| Disband the team | team_delete | team_run_id, force: true |
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.
Before starting, verify:
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 senpi without
--no-omo-task(the task component is on by default), then retry."
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 only when that category resolves in this project; if team_create rejects deep as unresolvable, retry once without only the researcher member and state the degraded roster.
test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.