# Closeout

> Close or park an explicit unit of work when the user invokes closeout. Use for deliberate state reconciliation, verification, receipts, and an optional handoff; never infer it from casual phrases such as “done” or “thanks.”

- Skill: `aylee/closeout` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add aylee/closeout`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aylee/closeout/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: aylee (https://skillmd.com/u/aylee)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aylee/closeout

---


# Close out

Treat closeout as a previewed transaction with independent effect boundaries.

## Preview

Read the owner binder, linked `WORKSTREAM.md`, relevant artifacts, and verification evidence. Present:

- outcome: shipped, completed locally, parked, or blocked;
- snapshot changes needed;
- receipt to create;
- unresolved risks or missing verification;
- optional effects: Git, PR, publishing, archive/tombstone, cross-repo memory, or handoff.

Ask before any optional effect not already authorized by the user’s request.

## Apply

1. Update the workstream to concise current truth and verification. Leave exactly one next action while active, parked, or blocked. Set `status: closed` only when nothing required remains, and use `None — closed.` as the exact terminal sentinel.
2. Create a uniquely named lifecycle receipt. Never append to a shared log.
3. Do not create a handoff unless a real agent, runtime, machine, parallel-lane, or context boundary exists. If one exists, suggest `$handoff`.
4. Give a human recap: outcome, what changed, evidence, remaining risk, and next action.

Git is optional evidence, not the state system. Never delete artifacts because Git might retain them, and never create a repository-local archive that conflicts with nearer policy.