diff --git a/skills/maka-cli/SKILL.md b/skills/maka-cli/SKILL.md
index 94ac41a9d5c..766ac8a1008 100644
--- a/skills/maka-cli/SKILL.md
+++ b/skills/maka-cli/SKILL.md
@@ -55,13 +55,22 @@ Wait when ready for the next interaction or result; avoid repeated status pollin
 ```sh
 maka run --session "$session" --status
 maka run --session "$session" --recap --json
-maka run --session "$session" "Inspect the tests next" --no-wait
+maka run --session "$session" "Inspect the tests next" --json
 maka run --session "$session" "Focus on the parser" --steer --no-wait
 ```
 
 Status returns lifecycle and pending interactions; `--status --recap` returns both state/boundary and progress as JSON. If installed help advertises `--recap`, use it to summarize recorded progress during execution. Each recap calls the model independently and can lag execution; it is neither final output nor a direct worker reply. Portable `session-export` is not a progress query.
 
-An added prompt queues by default; `--queue` is optional. `submission` confirms admission, while `status` describes the observed Session, possibly an earlier Turn. Service current questions/approvals before expecting queued work to execute. Status and admission receipts already return JSON; use `--json` on waits/results/recaps to keep their output structured.
+For an idle Session, send the next prompt and wait as above; `--no-wait` is only needed when intentionally detaching. A busy Session has status `running`, `needs_input`, or `needs_approval`. Submit its follow-up with `--no-wait`, then use Session-only waits to handle the current Turn's questions/approvals before queued work can execute:
+
+```sh
+maka run --session "$session" "Inspect the tests next" --no-wait
+maka run --session "$session" --wait --json
+```
+
+Waiting on the new prompt does not return an earlier Turn's interactions.
+
+An added prompt queues by default; `--queue` is optional. `submission` confirms admission, while `status` describes the observed Session, possibly an earlier Turn. Status and admission receipts already return JSON; use `--json` on waits/results/recaps to keep their output structured.
 
 ## Handle decisions and interruption
 
diff --git a/skills/maka-cli/references/session-control.md b/skills/maka-cli/references/session-control.md
index 7ecdaefe3d0..461f59bb4eb 100644
--- a/skills/maka-cli/references/session-control.md
+++ b/skills/maka-cli/references/session-control.md
@@ -56,7 +56,7 @@ Permission requests, MCP forms, and other unsupported kinds remain waiting when
 
 ## Queue, steering, and Inbox
 
-For coordination, submit a follow-up with `--no-wait`, then use Session-only wait/answer calls. Each queued message gets its own later Turn. Omit `--no-wait` and use `--json` only when following that message's exact result while separately servicing earlier Turns: that wait does not return an earlier Turn's AskUser and can leave the queue blocked.
+If the Session is idle, send the next prompt with `--json` and wait for its result or interaction. If it is busy (`running`, `needs_input`, or `needs_approval`), submit a follow-up with `--no-wait`, then use Session-only wait/answer calls to service the current Turn. Each queued message gets its own later Turn. Waiting on a follow-up selects that message's result and does not return an earlier Turn's AskUser, so it can leave the queue blocked.
 
 Steering is delivered at Host execution boundaries and can carry over if it misses the current Turn. Admission does not prove consumption. Steer with `--wait` observes the Turn selected on attachment. `--result` reads the latest Turn, not an arbitrary previous assignment.