close-work

# Skill: close-work Own closeout after delivery. `work-loop` returns implementation and verification evidence; it never chooses artifact retention or performs closeout. `workspace-status` may project eligibility and next actions, but it never distils, dispositions, confirms, compacts, or deletes. Only this workflow marks Closeout-pending or Post-closeout and proposes or applies an authorized closeout effect. Closeout is semantic extraction before container disposition. A disposition is intent, never deletion permission. Immediate disposal is a default recommendation, never an automatic action. ## Output rendering <!-- agentbundle:output-rendering:start --> Lead with the useful outcome or next action. Use warm, non-blaming language and everyday words. Define an unfamiliar term in a few plain words before naming it; keep proper names and exact technical terms intact. During tool work, do not narrate routine calls. Send an update only for safety, a blocker, a needed decision, a material scope change, a long wait, or an active host requirement. When requesting input, ask only for what is needed now. Ask dependent questions one at a time; otherwise group related questions. Offer no more than three clear choices when choices help. Shape the answer to the facts: one fact needs one sentence; related facts use prose; separate items use bullets; real sequences use numbered steps. For prose artifacts, use descriptive headings, short resumable sections, one fact per sentence, and no ...