Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

kyzo-plan-manage-board

Sterne3

Forks0

Aktualisiert16. Juli 2026 um 04:18

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

kyzodb

kyzodb/plan

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige ComputerberufeInformatik- und Mathematikberufe·SOC 15-1299

SKILL.md

readonly

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

kyzo-plan-manage-board

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.

Mehr aus diesem Repository

gleiches Repository

kyzo-plan-run-story

kyzodb/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.

2026-07-163

kyzo-plan-task-completion-request

kyzodb/plan

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

2026-07-163

kyzo-plan-write-epic

kyzodb/plan

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

2026-07-163

kyzo-plan-write-story

kyzodb/plan

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

2026-07-163

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

kyzo-plan-manage-board

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.