toki/iop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(agent-ops): 자식 실행 경계를 명시한다

Browse source 
dispatcher가 시작한 자식 에이전트가 orchestration을 재호출하지 않도록 실행 식별자와 허용된 PLAN 검증 범위를 계약에 고정한다.
This commit is contained in:
toki 2026-07-31 16:58:04 +09:00
parent 40f52da95f
commit 8760d16510
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
agent-ops/skills/project/orchestrate-agent-task-loop/SKILL.md
View file

@ -97,6 +97,9 @@ Concurrency limits:
Keep control prompts in English, insert absolute paths only, and do not expand these sentences unnecessarily.
- A dispatcher child runs only while `IOP_AGENT_TASK_EXECUTION_ID` is present.
- Prefix every child prompt with: `You are a child agent already launched by the dispatcher, not the orchestration caller. Execute only the assigned role directly. Do not start, monitor, or wait for orchestration through dispatch.py or orchestrate-agent-task-loop. You may run dispatch.py --validate-plan only when required by plan or code-review finalization because that mode validates one candidate PLAN without starting or monitoring orchestration.`
- Cloud worker: `Read {PLAN_PATH} and complete the task. Keep artifact content in English. Final in Korean.`
- Pi worker: `Think in English. Keep artifact content in English. Final in Korean. Read {PLAN_PATH} and complete the task.`
- Pi self-check: `Think in English. Keep artifact content in English. Final in Korean. Read {CODE_REVIEW_PATH} and fill every missing implementation field. Do not finish until all implementation fields are complete. This is a self-check of completed work, not a review. Read {PLAN_PATH} and finish any missing work. Recheck and fix your work.`