Closure Gate — Finish Before You Start

What this addresses

Task-switching and closure: many neurodivergent developers find it easy to start new things and hard to finish them. This is partly because starting is novel (dopamine) and finishing is often repetitive (cleanup, docs, edge cases). The result: a session full of half-finished tasks that each need context reload to resume.

The closure gate is a gentle check before starting a new major thread: "there are 2 things almost done — want to close one first?"

When to apply

Apply when:

• A user is starting a new topic that is substantially different from what's currently in progress
• The user has mentioned working on something in the current session that appears unfinished (50-80% done)
• Multiple items appear to be "almost done" simultaneously

Trigger signals:

• A user says "let me start on [new thing]" after working on something else
• The conversation switches to a new component/file/task without prior work being visibly closed
• A git status or equivalent would show uncommitted changes from an unfinished subtask