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
ONLY board read/write — plan MCP tools, never raw gh. Tool descriptions are role×verb. Not write-story or run-story.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kyzo-plan:kyzo-plan-manage-boardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Tool schemas are deferred — `ToolSearch` `select:<name>`. Between tools:
Tool schemas are deferred — ToolSearch select:<name>. Between tools:
Grammar: read_* pure (read_board_status first). start_*/finish_* gated — never stash around refusals. move_to_* free. Authoring verbs write content. delete_issues operator-only.
Model: column + order. Horizons on epics. Story horizon from parent. Sub-issue order = execution order.
Lifecycle: start_story → demolition → T#s (parent Check + judge + allowlist commit) → Final QA comment → check_final_qa → Done.
Spawning: kyzo-plan-run-story. Authoring: kyzo-plan-write-story / kyzo-plan-write-epic.
npx claudepluginhub kyzodb/plan --plugin kyzo-planCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.