Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug…
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
Test an oh-my-opencode-slim release candidate or bugfix before publishing. Use when validating a packed plugin artifact, release branch, crash fix, OpenCode runtime compatibility, or model-specific smoke test such as OpenCode 1.17.11 message transform…
Use when estimating how long a task will take: coding, writing, research, analysis, design, data work, or anything else AI can contribute to. Estimate for a human working with AI, not a human working alone, and separate AI-speed work from human and external…
Use when a request includes examples, samples, templates, or reference outputs. Treat them as evidence of intent, not as something to copy: infer the principle behind them and produce something original at that level.
Use when a task keeps growing through patches: repeated fixes, workarounds, compatibility shims, or a new path built beside an old one. Pause, reassess the direction, and propose a cleaner alternative before continuing.
Use before implementing a feature, bug fix, refactor, or cross-system change to plan a credible project-specific verification path.