claude

kyzo-plan

The Kyzo Work board as typed MCP tools with a gated epic/story lifecycle.

5 on GitHubby Kyzov0.2.8BUSL-1.1updated 3 months ago
/

Plugin kyzo-plan from marketplace kyzo in kylejtobin/plan. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (5)

  • kyzo-plan-manage-board

    ONLY board read/write — plan MCP tools, never raw gh. Tool descriptions are role×verb. Not write-story or run-story.

  • kyzo-plan-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.

  • kyzo-plan-task-completion-request

    Minimal completion_request the development-task sends to the judge after allowlist edits. Not board writes, not git, not tree meters.

  • kyzo-plan-write-epic

    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).

  • kyzo-plan-write-story

    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).

Subagents (3)

  • kyzo-plan-demolition

    RUN FIRST after start_story — delete Condemned paths only. Red tree OK; preservation fails. Parent arms condemned allowlist and path-monitors. No Bash, git, or build. Not development or judge.

  • kyzo-plan-development-task

    Execute ONE story T# under allowlist — Edit/Write only, then kyzo-plan-task-completion-request to the judge. After demolition. Spawn via task_spawn XML. No Bash, git, or board mutate. Not demolition or judge.

  • kyzo-plan-task-completion-judge

    Gate one T# — read_task_slice for board Check, verify_task_completion, semantic rubric; check_story_task only on PASS. No repo browse, no help, no check_final_qa.

MCP servers (1)

  • board

    runs: uv run --project ${CLAUDE_PLUGIN_ROOT} python ${CLAUDE_PLUGIN_ROOT}/app/main.py

Hooks (1)

  • PreToolUse

    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kyzo_allowlist_guard.py"

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain kyzo-plan?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted