kata-execute-issue

Use when the user wants to execute a standalone Kata issue, one-off issue plan, backlog issue, or isolated implementation plan created by kata-plan-issue. This skill selects or retrieves an open issue from the backend, confirms the issue with the user, then executes its approved plan with fresh subagents and two-stage review per task.

Jump to install

Repository: gannonh/kata-symphony
Last source activity: May 6, 2026 at 01:34
Detected SKILL.md language: English
Stars: 58
Forks: 6

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/gannonh/kata-symphony --skill kata-execute-issue

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

13 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

plan-build-verify-github

Use this skill for multi-step, spec-driven, or acceptance-gated implementation work in a GitHub repository where specs live as GitHub Issues. Routes work through Plan, Build, and Verify phases, manages the roadmap through issue labels and sub-issues, and triages and grooms the backlog. Also handles migration from file-based specs to GitHub Issues.

2026-08-04

okf

Create, read, and maintain Open Knowledge Format documentation bundles in repositories. Use this skill when the user asks for /okf, OKF, Open Knowledge Format, docs-as-knowledge, reading project context from docs, reorganizing docs into an agent-readable bundle, updating docs/specs/ADRs after a session or PR, or adding AGENTS.md instructions for agents to consume and maintain the docs bundle. Supports /okf read, /okf init, and /okf update workflows.

2026-08-04

releasing-kata

Use this skill when releasing Kata CLI, Symphony, or the Pi Symphony extension, bumping versions, updating changelogs, or creating release PRs. Triggers include "release", "bump version", "publish", "create release PR", "ship it", "cut a release".

2026-06-23

View all from this repository

kata-execute-issue

Operating Brief

When this skill is invoked, execute one standalone backend issue created by kata-plan-issue in a backend that supports issue operations.

If the user did not provide an issue reference, list open standalone issues with issue.listOpen and ask the user to choose. If the user provided an issue number, Kata ID, or partial title, match it against open standalone issues, retrieve the matching issue with issue.get, summarize it with a link, and ask for confirmation before execution.

After confirmation, follow subagent-driven development as closely as possible: fresh implementer subagent per task, spec compliance review first, code quality review second, review loops until approved, then the next task. Update the issue status through issue.updateStatus.

Success Criteria

The selected standalone issue is confirmed by the user before execution starts.

The issue design and plan are retrieved from the backend, not from a local markdown plan file.

Each plan task is implemented by a fresh subagent with full task text and curated context.

Each task passes spec compliance review before code quality review starts.

Reviewer findings are fixed and re-reviewed before moving to the next task.

A final whole-change code review runs after all tasks complete.

The backend issue status reflects real execution state.

Do Not

Do not execute without confirming the selected issue with the user.

Do not load all open issue bodies when listing issues; use issue.listOpen summaries first.

name	kata-execute-issue
description	Use when the user wants to execute a standalone Kata issue, one-off issue plan, backlog issue, or isolated implementation plan created by kata-plan-issue. This skill selects or retrieves an open issue from the backend, confirms the issue with the user, then executes its approved plan with fresh subagents and two-stage review per task.