Menu
Use when the user wants to start, define, import, or initialize a Kata project.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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.
| name | kata-new-project |
| description | Use when the user wants to start, define, import, or initialize a Kata project. |
When this skill is invoked, help the user initialize durable Kata project context.
Start conversationally. If the user has not already provided enough detail, ask: "What do you want to build?" Follow their thread until you can explain the project, why it matters, who it is for, what done looks like, and what is explicitly out of scope.
Before durable writes, run node ./scripts/kata-call.mjs health.check. Then confirm the synthesized project brief with the user, run project.upsert, and write project-scoped artifacts with artifact.write.
This skill captures project-level context only; milestone scope and roadmap creation happen next in kata-new-milestone.
project.upsert.project-brief artifact captures what is being built, core value, users, context, constraints, decisions, and open questions.requirements artifact is written when concrete requirement hypotheses emerged.kata-new-milestone.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.mjsAdditional references:
references/questioning.mdreferences/ui-brand.mdTemplates:
templates/project.mdtemplates/requirements.mdreferences/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.