القائمة
Minimal completion_request the development-task sends to the judge after allowlist edits. Not board writes, not git, not tree meters.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
ONLY board read/write — plan MCP tools, never raw gh. Tool descriptions are role×verb. Not write-story or run-story.
Parent after start_story — arm paths, spawn demolition then each T#, run board Check, spawn judge, allowlist-commit on PASS / path-restore on FAIL, Final QA verdict then check_final_qa. Not write-story or manage-board.
Author or revise board epics — name + outcome as the value state the story group creates. Not story contracts (write-story), not T# runs (run-story), not column moves (manage-board).
Author or revise board story contracts (name, sources, condemned, ceiling, choice, allowlisted T#s, Final QA DoD). Not epic authorship (write-epic), not T# execution (run-story), not raw board moves (manage-board).
| name | kyzo-plan-task-completion-request |
| description | Minimal completion_request the development-task sends to the judge after allowlist edits. Not board writes, not git, not tree meters. |
Submit only this block to the judge. Do not invent paths, commands, or git output — the judge loads the board and runs verify_task_completion.
<completion_request>
STORY: <number>
TASK: T# — <exact board text>
COMPLETION CLAIM: <one sentence>
IMPLEMENTATION:
- <path:symbol or file you changed>
DEVIATIONS: None | <what blocked the slice>
STORY OR TASK CHANGES: None | <proposed change — do not apply it>
</completion_request>
Done is judge PASS only.