feature-close
Installation
SKILL.md
Feature Close
Finish one explicitly targeted Feature after any implementation skill, agent team, or human execution path reports that it is done. This is a closeout gate, not an implementation workflow.
Resolve the target
- Read repository instructions, the exact Feature record, its Task plan and child Task records, the optional Milestone, configured tracker, and current Git branch/worktree state.
- Prefer a Feature ID, link, path, or name from the request. Otherwise resolve the current actor from the request,
.waypoint/local.yaml, or the external tracker and filter active Features by owner. - Continue only when exactly one Feature remains. Ask when none or several remain. Never choose another owner's Feature, the first ready item, recent work, Git history, or branch naming.
- Reuse the Feature owner from its record or tracker. Only that owner may confirm Feature completion.
Audit completion before integration
Treat Acceptance as the durable completion checklist. Inspect every applicable checkbox and its evidence; do not infer completion from a successful build, a commit, or an implementation agent's done message.
- Task: for every child Task, require every Task Acceptance item to be
[x], task-local verification to pass, review corrections to be resolved, and any required Task integration to be complete. An unsplit Feature has no Task-level gate. - Feature: require every Feature Acceptance item to be
[x], the Feature-level verification and integration proof to be recorded, and no unresolved blocker to remain. - Milestone: when the Feature belongs to a Milestone, require the Feature's Milestone entry and every exit criterion it owns to be
[x]or explicitly covered by the accepted Feature evidence. Do not close a Milestone merely because this Feature is complete; sibling Features and remaining exit criteria still belong to the coordinator.