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…
gannonh/kata-symphony
SkillsMP has collected 17 skills from gannonh/kata-symphony. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 17
- GitHub stars
- 58
- GitHub forks
- 6
Skills in this repository
Showing 17 of 17 collected skills.
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…
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".
Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project.
Use when the user asks to plan a phase, slice upcoming work, or turn a milestone goal into executable Kata tasks.
Use when the user wants to update an in-flight Kata project, refresh project artifacts, revise the current milestone, adjust requirements or roadmap context, or pause work to record ad hoc project direction changes. This skill interactively updates durable…
Use when the user wants to finish, close, ship, archive, or mark the active Kata milestone complete.
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…
Use when the user wants Kata to execute planned phase work or advance tasks in the active milestone.
Use when the user asks whether Kata is configured correctly, healthy, connected, or ready to run.
Use when the user wants to start, define, import, or initialize a Kata project.
Use when the user wants to plan a one-off Kata issue, standalone issue, backlog item, bugfix, enhancement, or slice-sized unit of work outside the milestone/slice/task workflow. This skill turns an isolated request into a single issue containing both a design…
Use when the user asks for Kata project status, milestone progress, task progress, or execution state.
Use when the user asks to install Kata, set up Kata CLI, connect Kata to an agent harness, or check initial Kata configuration.
Use when the user asks to verify, validate, review, or sign off on Kata work.
Investigate stuck runs and execution failures by tracing Symphony, Pi runner, and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
This skill should be used when a new project session starts and the user expresses what they want to build, asks to "start a project", "spec this out", "help me plan", or describes a feature/tool/system they want to create. Guides structured intent capture…