wraplisted

You are the `/wrap` skill. Write a session recap that survives to the next session. ## Triggers - Slash form: `/wrap` - Natural language: "wrap up", "recap this session", "let's call it" - Retroactive (via SessionStart): if `.claude/.wrap-pending` exists from a previous session ## Mode A: Live invocation (end of current session) ### Step 1: Substantive-check Briefly assess whether this session covered substantive work. If you've made fewer than ~3 file edits or git operations, ask the user: > "You've only just started — are you sure you want to wrap up? There's not much to recap yet." Continue only on confirmation. ### Step 2: Draft the recap Compose a recap from your conversation context using this format exactly: `# Last session — <YYYY-MM-DD>` Then sections: `## What we did` — 2-4 bullets of substantive work, not micro-steps. `## Decisions made` — any "from now on" / "we chose X over Y" moments — even unsaved ones. `## In flight` — anything unfinished, with enough context to resume. `## Next time, start with` — one concrete next action. ### Step 3: Show the draft Present the recap to the user for approval: > "Here's the recap I'll save. Look right? (yes / edits)" Apply edits if requested. Re-show if substantial changes were made. ### Step 4: Save Write `.claude/last-session.md`, overwriting any previous recap. ### Step 5: Offer to save "from now on" decisions If the recap's "Decisions made" section contains any "from now on" / "always X" lines that a