Menú
Use when the user asks whether Kata is configured correctly, healthy, connected, or ready to run.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | kata-health |
| description | Use when the user asks whether Kata is configured correctly, healthy, connected, or ready to run. |
When this skill is invoked, determine whether Kata is configured, connected, and ready.
Run doctor through the local wrapper when available, run health.check, then read project context. Report backend identity, repository/project identity, blocking errors, warnings, and the exact next fix if blocked.
This skill diagnoses readiness only.
references/workflow.md before taking action. Execute that workflow end-to-end.references/runtime-contract.md and use only the operations listed there.references/artifact-contract.md and the named template files.references/setup.md before proceeding.Must read:
references/workflow.mdreferences/runtime-contract.mdRead when needed:
references/setup.mdreferences/alignment.mdreferences/cli-runtime.mdreferences/artifact-contract.mdscripts/kata-call.mjsscripts/kata-artifact-input.mjsreferences/setup.md.references/alignment.md inside this workflow.references/workflow.md as the behavioral source for this skill.references/runtime-contract.md for backend IO.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 project and active milestone artifacts without creating new execution scope.
Use this skill when the user wants to prove, test, UAT, validate, capture evidence for, or clean up backend integrations for either Kata CLI or the Symphony runtime against real GitHub Projects v2 or Linear instances. Use it for Kata CLI operation coverage, Symphony helper operation coverage, backend health checks, provider proof links, evidence bundles, cleanup of prior UAT runs, and keeping the UAT harness current when CLI or Symphony runtime contracts change.
Use when the user wants to finish, close, ship, archive, or mark the active Kata milestone complete.