Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Kyzo Plan
Minimal completion_request the development-task sends to the judge after allowlist edits. Not board writes, not git, not tree meters.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kyzo-plan:kyzo-plan-task-completion-requestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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`.
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.
npx claudepluginhub kyzodb/plan --plugin kyzo-planCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.