| name | kata-complete-milestone |
| description | Use when the user wants to finish, close, ship, archive, or mark the active Kata milestone complete. |
kata-complete-milestone
Operating Brief
When this skill is invoked, close the active release-sized milestone after all milestone slices and tasks are done and verified.
Load the project snapshot and active milestone, list slices, list tasks for each slice when detail is needed, inspect milestone/slice/task artifacts, read project-scoped closeout artifacts, confirm every required task is done and verified, summarize delivered outcomes, capture retrospective notes, write milestone completion artifacts, update project closeout artifacts, and then complete the milestone through milestone.complete.
If readiness is uncertain, stop and explain what must be verified or resolved first.
Success Criteria
- The active milestone has an accepted completion summary.
- Every required slice is done.
- Every required task is done with
verificationState: verified.
- Completion evidence includes milestone, slice, task, and project-scoped artifacts.
- Retrospective or archive artifacts are persisted when useful.
- Project brief and project requirements artifacts are updated before
milestone.complete, or the workflow stops to repair missing project artifacts.
- Existing milestone summary, retrospective, and project closeout artifacts are updated idempotently when they already exist.
- Carry-forward requirements are only reclassified after explicit confirmation and evidence.
- Completion output names the project tracking issue when the backend reports it and reports what changed in the project artifacts.
- The milestone is completed through
milestone.complete only after readiness is confirmed and closeout artifact writes succeed.
- The user knows what remains, if anything, after completion.
