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-openagent
github-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'.
193pre-publish-review
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Use before EVERY npm publish. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
165work-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.
162git-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'.
6agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
2