wrapup

Writes session narrative logs, hand-off prompts, and board sweep results to a state repository.

1|Updated Nov 21, 2015
One-click install
npx skills add https://github.com/mark-brannan/dotfiles --skill wrapup-mark-brannan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrapup
Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/wrapup
Command: npx skills add https://github.com/mark-brannan/dotfiles --skill wrapup-mark-brannan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a work session without losing context is hard: decisions, abandoned approaches, and open loops vanish when the chat closes. This Skill closes a session properly by recording what the session meant, producing a paste-ready hand-off prompt for the next session, and sweeping the kanban board for unresolved cards. ## Core Features & Use Cases - Archivability check: Reads the auto-checkpoint verdict first and skips the full wrap-up when the work already has a home (PR, issue, or card), avoiding duplicate records. - Narrative log: Writes a dated markdown log to the state directory capturing decisions with links, abandoned attempts, and next steps. - Hand-off prompt generation: Produces a paste-ready prompt naming the branch, PR, or issue, with links instead of stale state, plus a recommended model and effort setting. - Board sweep: Runs /sweep --dry-run last and records its output in the log. - Use Case: At the end of a coding session with open issues, say "wrap up" to get a narrative log committed to the state repo and a hand-off prompt the next session can start from. ## Quick Start Say "wrap up this session" to generate the narrative log, hand-off prompt, and board sweep summary.

Frequently Asked Questions about wrapup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off an unfinished coding session to the next session?▼

Invoke the wrap-up flow to write a narrative log and a paste-ready hand-off prompt naming the branch, PR, or issue. If the work already lives on a PR or issue, the hand-off is a single continue link with lessons posted as a comment.

What should a session hand-off prompt include?▼

A hand-off prompt must be paste-ready, name the branch or PR it acts on, carry links instead of state adjectives, rate each item's difficulty for both a human and an agent, and name a recommended model and effort setting.

When should a session skip the full wrap-up?▼

Skip it when the auto-checkpoint verdict is archivable: the branch has a PR, the worktree is clean, nothing is unpushed, and every open loop has a home. In that case state where the work lives in one line and stop.

Why run the board sweep after writing the log and hand-off?▼

The sweep is the slow step at roughly four seconds per card, so running it last guarantees the log and hand-off prompt survive even if the session is cut short. Its output is then appended to the narrative log.

Does the wrap-up duplicate what the Stop hook already records?▼

No. The Stop hook writes the session record, decision log, and auto-checkpoint automatically. The wrap-up only adds what automation cannot: what the session meant, what remains open, and how the next session should start.