From Kyzo Plan
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kyzo-plan:kyzo-plan-run-storyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Children deviate. Unwatched deviation is your fault.
Children deviate. Unwatched deviation is your fault.
| You | Children never |
|---|---|
start_story, arm session, spawn, path-monitor | git, Bash, board mutate, check_story_task |
| Run board Check before judge | invent a greener check |
| Allowlist-only commit after judge PASS (that commit is the seal) | stash / hard-reset / worktree / off-list commit |
| Path restore on FAIL | |
Final QA verdict (comment) then check_final_qa | skip the written verdict |
move_to_done | Witness / CI orchestration |
One epic branch. One writer at a time.
python3 ${CLAUDE_PLUGIN_ROOT:-mcp}/scripts/kyzo_arm_session.py <paths...>
export KYZO_TASK_SESSION="$(pwd)/.kyzo/task-session.json"
kyzo-plan-demolition with XML naming only those paths + condemned text.<demolition_spawn>
<story>#N</story>
<allowlist>
<path>…condemned path…</path>
</allowlist>
<condemned>…</condemned>
</demolition_spawn>
read_task_slice → arm Allowlist paths.kyzo-plan-development-task:<task_spawn>
<story>#N</story>
<task>T# — exact board text</task>
<allowlist>
<path>…</path>
</allowlist>
<check>…exact board Check…</check>
<context_refs>…</context_refs>
</task_spawn>
| Tell | Action |
|---|---|
| path ∉ allowlist | whip |
Bash / git / board mutate / check_story_task | whip; second → kill |
| 5 tools, zero Edit/Write | whip |
| second offense | kill |
<completion_request> only.git add -- <allowlist paths only> → one commit (T# — …). Then next T#.git restore --worktree --staged -- <allowlist paths only>. Never reset --hard / stash.Write a story comment:
FINAL QA
VALUE: …
CONDEMNED: …
CHOICE: …
SOURCES: …
Then check_final_qa → move_to_done (or next story).
Dirty tree at start_* → escalate to operator. Stash to pass a gate = fraud.
See references/gotchas.md and references/examples.md.
npx claudepluginhub kyzodb/plan --plugin kyzo-planCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.