Menu
Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project.
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.
Based on SOC occupation classification
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 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.
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.
| name | kata-new-milestone |
| description | Use when the user wants to create the next milestone, release goal, or scoped delivery target for an existing Kata project. |
When this skill is invoked, help the user define the next scoped delivery milestone for an existing Kata project.
Start by reading project context and recent completed milestone artifacts, then ask what outcome the next milestone should deliver. Gather enough detail to define the milestone goal, requirements, roadmap, constraints, open questions, and any carry-forward candidates.
Create exactly one milestone with milestone.create, then write milestone-scoped requirements and roadmap artifacts with artifact.write. Shape the roadmap as demo-able vertical slices with minimized dependencies and explicit parallelization opportunities. End by routing the user to kata-plan-phase.
requirements artifact.roadmap artifact.kata-plan-phase.kata-new-project.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.mdtemplates/roadmap.mdtemplates/state.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.