Problem
What problem this solves
Work often ends in an ambiguous state where the code changed, but the task record, changelog, or summary did not.
Skill Detail
Close a task cleanly so the work is summarized, tracked, and ready for the next thread.
A task-closing skill for wrapping up implementation, documenting completion, and recording closure in the chantier flow when applicable.
Problem
Work often ends in an ambiguous state where the code changed, but the task record, changelog, or summary did not.
Outcome
You get a cleaner end-of-task handoff with explicit closure signals instead of loose thread residue.
Why It Matters
This skill helps you avoid the classic 'done in code, unclear everywhere else' problem that slows future sessions.
Related Skills
Check whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill pageReview recent work and the session state before you lose the thread of what changed.
A review skill for summarizing recent changes, identifying remaining gaps, and updating local workflow state cleanly.
Open skill pageCommit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.