fix(docs): correct plan invocation syntax from /plan to @plan

code-yeongyu · code-yeongyu · commit 5242f3daef91 · 2026-01-09T17:45:25.000+09:00
OpenCode uses @agent-name syntax for agent invocation, not /command. The /plan command does not exist - it should be @plan to invoke the Prometheus planner agent.
diff --git a/docs/orchestration-guide.md b/docs/orchestration-guide.md
@@ -6,7 +6,7 @@
 |------------|----------|-------------|
 | **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. |
+| **Complex + Precise** | `@plan` → `/start-work` | Precise, multi-step work requiring true orchestration. Prometheus plans, Sisyphus executes. |
 
 **Decision Flow:**
 ```
@@ -15,7 +15,7 @@ Is it a quick fix or simple task?
   └─ 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
+                        └─ YES → Use @plan for Prometheus planning, then /start-work
                         └─ NO  → Just use "ulw"
 ```
 
@@ -114,9 +114,9 @@ When the user enters `/start-work`, the execution phase begins.
 
 ## 5. Commands and Usage
 
-### `/plan [request]`
+### `@plan [request]`
 Invokes Prometheus to start a planning session.
-- Example: `/plan "I want to refactor the authentication system to NextAuth"`
+- Example: `@plan "I want to refactor the authentication system to NextAuth"`
 
 ### `/start-work`
 Executes the generated plan.
