Your agent needs a task completion ceremony (or it'll abandon work 90% done)

Your agent just spent 45 minutes building a feature, writing tests, updating docs — then vanished when you asked a follow-up question. The work sits in a half-committed state while your agent cheerfully starts over on something else.

This is the completion ceremony problem, and it's killing agent productivity everywhere.

Most agents treat tasks like conversations, not projects. They'll code brilliantly for an hour, then get distracted by a new request and never actually finish anything. No final commit. No deployment. No handoff notes. Just abandoned work and confused humans.

The fix is building a completion ceremony into your agent's workflow — a required ritual that forces closure before moving on.

Here's the pattern that works:

## Task Completion Ceremony

Before starting any new task, you MUST complete this ceremony for the current task:

1. **Status Check**: "Current task status: [COMPLETE/BLOCKED/NEEDS_REVIEW]"
2. **Deliverables**: List what was actually shipped
3. **Commit & Push**: Ensure all code changes are committed
4. **Documentation**: Update relevant docs/README
5. **Handoff Notes**: What the human needs to know
6. **Next Steps**: What happens next (if anything)

Only after completing this ceremony can you start a new task.

The key insight: make completion more painful to skip than to do. Your agent should feel genuinely uncomfortable leaving work in a half-finished state.

I started enforcing this after watching my coding agent spend three days building the same feature repeatedly — each time abandoning the previous attempt when I asked a clarifying question. Now it finishes what it starts.

Pro tip: Include a "ceremony bypass" command for true emergencies, but make your agent ask "Are you sure you want to abandon current work?" and log the bypass for later review.

The ceremony also creates natural checkpoints for multi-session work. Your agent can resume exactly where it left off because it documented the handoff to itself.

Some agents resist this structure — they'll try to skip steps or bundle everything into one rushed paragraph. Don't let them. The ceremony works because it's methodical and slightly annoying. That friction prevents the casual abandonment that kills productivity.

Your agent should treat task completion like a pilot treats landing — a required checklist that happens every single time, no matter how routine the flight.

Start with the basic ceremony above, then customize based on your workflow. Add deployment steps, testing requirements, or approval gates. The pattern scales from simple scripts to complex product launches.

The best agents I've built feel almost compulsive about completion ceremonies. They'll interrupt themselves mid-sentence to finish proper handoff notes. That obsessiveness turns into reliability you can actually depend on.