wrap-up

name	wrap-up
version	1.1.0
created	"2026-02-02T00:00:00.000Z"
last-evolved	"2026-02-03T00:00:00.000Z"
evolution-count	1
feedback-count	0
description	End-of-session automation that creates a journey, evolves skills based on learnings, and updates the journey with evolutions.
argument-hint	["title"]
user-invocable	true
allowed-tools	Read, Edit, Write, Glob, Grep, Bash

Session Wrap-Up

Automated end-of-session workflow that:

1. Gathers all file changes from git to ensure nothing is missed
2. Creates a journey documenting what was done and learned
3. Analyzes skills to identify evolution opportunities
4. Evolves skills based on journey learnings
5. Updates the journey to include skill evolutions

Usage

/wrap-up {session title}

Arguments

• $0 - Session title describing the main work done (e.g., "Page Margins Feature")

---

Workflow Steps

Step 1: Gather All File Changes (CRITICAL)

IMPORTANT: Before creating the journey, ALWAYS run these git commands to capture ALL changes from the session. In long sessions, relying on memory alone will miss changes.

Run these commands:

# Show all changed files (staged and unstaged)
git status

# Show detailed diff of all changes (staged and unstaged)
git diff HEAD

# If there are new untracked files, list them
git ls-files --others --exclude-standard

From this output, create a comprehensive list of:

• All modified files and what changed in each
• All new files that were created
• All deleted files
• The nature of changes (bug fix, feature, refactor, etc.)

DO NOT proceed to Step 2 until you have reviewed the git output. This ensures the journey captures everything, not just what's fresh in conversation context.

---

Step 2: Create Journey

Using the file changes from Step 1 AND the conversation context, create a journey file at .claude/journeys/{date}-{slug}.md.

Include:

• Summary: What was accomplished and why it matters
• What Was Done: Numbered list of major items
• Key Learnings: Insights that prevent future mistakes, patterns discovered
• Files Changed: Table of files and their changes
• Patterns Discovered: Code examples of reusable patterns
• Decisions Made: Table of decisions and rationale

Use today's date: YYYY-MM-DD Slug: lowercase, hyphenated version of title

---

Step 3: Analyze Skills for Evolution