hyperplan
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 into a work plan.
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.
HARD PRECONDITIONS
Before starting, verify:
team_*tools must be available. If they are not, STOP and tell the user:"Hyperplan requires team-mode. Set
team_mode.enabled: truein~/.config/opencode/oh-my-opencode.jsoncand restart opencode, then retry."- You are running as
sisyphus(or another lead-eligible agent). If you are running as a planner (prometheus,plan), this skill is the wrong tool — direct the user to use/start-workinstead. - You are in the main session (not a background subagent). Hyperplan only works as a top-level orchestration.
More from code-yeongyu/oh-my-opencode
github-issue-triage
Triage GitHub issues with streaming analysis. CRITICAL: 1 issue = 1 background task. Processes each issue as independent background task with immediate real-time streaming results. Triggers: 'triage issues', 'analyze issues', 'issue report'.
1.3Kgithub-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
805frontend-ui-ux
Designer-turned-developer who crafts stunning UI/UX even without design mockups
255github-pr-triage
Triage GitHub Pull Requests with streaming analysis. CRITICAL: 1 PR = 1 background task. Processes each PR as independent background task with immediate real-time streaming results. Conservative auto-close. Triggers: 'triage PRs', 'analyze PRs', 'PR cleanup'.
96git-master
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
93work-with-pr
Full PR lifecycle: git worktree → implement → atomic commits → PR creation → verification loop (CI + review-work + Cubic approval) → merge. Keeps iterating until ALL gates pass and PR is merged. Worktree auto-cleanup after merge. Use whenever implementation work needs to land as a PR. Triggers: 'create a PR', 'implement and PR', 'work on this and make a PR', 'implement issue', 'land this as a PR', 'work-with-pr', 'PR workflow', 'implement end to end', even when user just says 'implement X' if the context implies PR delivery.
92