From aa5018583e757be02b8973ea55573670855e8646 Mon Sep 17 00:00:00 2001 From: YeonGyu-Kim Date: Fri, 9 Jan 2026 16:47:04 +0900 Subject: [PATCH] docs(orchestration): add TL;DR section for quick reference --- docs/orchestration-guide.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/orchestration-guide.md b/docs/orchestration-guide.md index 550b97df8..41cc6058e 100644 --- a/docs/orchestration-guide.md +++ b/docs/orchestration-guide.md @@ -1,5 +1,26 @@ # Oh-My-OpenCode Orchestration Guide +## TL;DR - When to Use What + +| Complexity | Approach | When to Use | +|------------|----------|-------------| +| **Simple** | Just prompt | Simple tasks, quick fixes, single-file changes | +| **Complex + Lazy** | Just type `ulw` or `ultrawork` | Complex tasks where explaining context is tedious. Agent figures it out. | +| **Complex + Precise** | `/plan` → `/start-work` | Precise, multi-step work requiring true orchestration. Prometheus plans, Sisyphus executes. | + +**Decision Flow:** +``` +Is it a quick fix or simple task? + └─ YES → Just prompt normally + └─ NO → Is explaining the full context tedious? + └─ YES → Type "ulw" and let the agent figure it out + └─ NO → Do you need precise, verifiable execution? + └─ YES → Use /plan for Prometheus planning, then /start-work + └─ NO → Just use "ulw" +``` + +--- + This document provides a comprehensive guide to the orchestration system that implements Oh-My-OpenCode's core philosophy: **"Separation of Planning and Execution"**. ## 1. Overview