wrap-up

Capture session outcomes and update notes, metadata, and knowledge artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/popodidi/harvis --skill wrap-up-popodidi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/popodidi/harvis/tree/main/projects/self/skills/wrap-up
Command: npx skills add https://github.com/popodidi/harvis --skill wrap-up-popodidi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and individuals capture session outcomes, document learnings, and finalize work artifacts so knowledge is preserved and progress is traceable.

Core Features & Use Cases

  • Session wrap-up: End a work session while preserving context for continuity (what was done, what's next).
  • Memory wrap-up: Finalize a completed memory/task and extract learnings, improvements, and backlog for future work.
  • Command triggers: Use /wrap-up, /wrap-up session, or /wrap-up memory to drive the workflow, automatically updating metadata.yaml, notes.md, learnings.md, improvements.md, and backlog.md as appropriate.

Quick Start

Use the wrap-up skill to update the latest memory or session state and commit the changes across metadata and notes.

Frequently Asked Questions about wrap-up

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

FAQPage Schema
How do I capture session learnings and preserve work context for future continuity?

To capture session learnings and preserve context, you can trigger a session wrap-up workflow that automatically updates notes.md, learnings.md, and metadata.yaml with what was done and what comes next.

What's the best way to document task learnings and update a backlog after completing a memory?

Documenting task learnings and updating a backlog is handled by the memory wrap-up mode, which finalizes completed tasks by extracting insights and writing them into learnings.md, improvements.md, and backlog.md.

How does automatic metadata and notes synchronization work when finalizing work sessions?

Automatic metadata and notes synchronization works by checking for skill changes, syncing skills, and committing the final state across metadata.yaml and notes.md when you invoke the wrap-up workflow.

Can I use session wrap-up for ongoing work without finalizing completed tasks prematurely?

Yes, session wrap-up is designed specifically for ongoing work continuity, preserving what was done and what is next, while memory wrap-up is used separately to finalize completed tasks.

What files are updated when I run a wrap-up workflow for memory management?

Running a wrap-up workflow for memory management updates metadata.yaml, notes.md, learnings.md, improvements.md, and backlog.md as appropriate to the triggered mode.

When should I avoid using memory wrap-up instead of session wrap-up for knowledge artifacts?

You should avoid using memory wrap-up when work is still ongoing, as it finalizes completed tasks and extracts learnings, whereas session wrap-up is meant to preserve context for future sessions.