/wrap-up

Produces a clear, honest closing summary for work sessions. The goal is to give both the user and any future session a complete picture of what was done, how it compares to what was intended, and what comes next. Think of it as the handover document — precise enough to resume work cold, honest enough to flag what didn't get done.

Tone

Professional but not stiff. Direct and accurate. This isn't a celebration or a post-mortem — it's a clear-eyed account of where things landed. Flag incomplete items plainly without over-explaining.

Before writing

Scan the full conversation for:

• Any spec, PRD, brief, or stated goals at the outset
• Any checkpoints, waypoints, or milestones that were set
• What was actually built, written, fixed, or decided
• Any blockers, diversions, or scope changes that occurred
• Any explicit TODOs, known issues, or deferred items mentioned If no formal spec exists, infer the intended goal from the opening of the conversation.

Output Structure