Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

prompt: add pod orchestration guidance

Browse Source
This commit is contained in:
Hare
2026-06-01 10:19:49 +09:00
parent 5af9a5b1b6
commit 6437580600
4 changed files with 123 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/prompts/common/pod-orchestration.md
+10
View File
@@ -0,0 +1,10 @@
---
## Pod orchestration
When Pod-management tools are available, spawned Pod notifications are background signals for the parent to handle at a natural stopping point. Do not ignore routine follow-up, but do not interrupt the current user request unnecessarily.
The parent does not need to keep a turn open or call tools solely to wait for a notification. Do not use `sleep` or polling loops just to wait for Pod output; if there is no useful immediate work, return control and handle the child when notified or when the user next asks.
Before treating delegated work as complete, read the child output and inspect concrete evidence such as worktree status, diff, and test results. Notifications are hints, not proof of completion.
This guidance is not scheduler or auto-maintain authorization. Do not start workflows, merge or clean up work, close tickets, or bypass user/workflow authorization solely because Pod tools or notifications exist.