wrapup

Summarize work-session outcomes and update project-local state files.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/shawnpetros/claude-skills --skill wrapup-shawnpetros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrapup
Source: https://github.com/shawnpetros/claude-skills/tree/main/wrapup
Command: npx skills add https://github.com/shawnpetros/claude-skills --skill wrapup-shawnpetros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ending a work session often leaves you with scattered decisions and transient context, making it hard to remember what shipped, what’s blocked, and what to do next.

Core Features & Use Cases

  • Session wrapup automation: Closes out substantive sessions by promoting durable outcomes into long-term notes and updating local project state.
  • Project-state refresh: Rewrites SESSION-CONTEXT.md and updates features.json for only the items actually discussed, keeping cross-session context accurate.
  • Clean version control checkpoint: Creates a targeted commit for the updated session artifacts to make progress auditable and reproducible.

Quick Start

Run wrapup when you’re done for the day (or use /wrapup) so it promotes your session outcomes to project notes, rewrites SESSION-CONTEXT.md, updates features.json, and prepares a commit.

Frequently Asked Questions about wrapup

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

FAQPage Schema
How do I automate session wrapup to save project context and decisions?

Automate session wrapup by summarizing conversation outcomes into a durable history entry, rewriting SESSION-CONTEXT.md, selectively updating features.json, and committing the changes. This converts transient work sessions into lasting, auditable project progress.

What is the best way to log decisions and update project context after a coding session?

The best way to log decisions is promoting a one-line history entry to project pages and rewriting SESSION-CONTEXT.md. This updates local project state with only the items actually discussed, ensuring cross-session context remains accurate and clean.

How do I prepare a clean git commit for project state updates when ending a session?

Prepare a clean git commit by summarizing session outcomes and updating local artifacts like features.json and SESSION-CONTEXT.md. The wrapup process creates a targeted version control checkpoint containing only relevant changes for reproducible progress.

When should I rewrite SESSION-CONTEXT.md for cross-session context handoff?

Rewrite SESSION-CONTEXT.md when a session ends, such as when you are wrapping up or thanking the assistant, or when context gets too long and a clean handoff to future work is needed to maintain accurate project state.

Does session wrapup require reading a daily digest before updating features.json?

Session wrapup requires reading an optional daily digest to inform the process. It uses this input to selectively update features.json for only the items actually discussed during the session, preventing unwanted state overwrites.

Can I update features.json selectively based on session outcomes instead of the whole project?

You can selectively update features.json based on session outcomes. The wrapup mechanism parses work-session conversation history and applies targeted updates to features.json only for the specific items actually discussed, keeping local state accurate.