wrap-up-ritual

Capture completed work, pending tasks, and insights into .claude/handoff.md.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill wrap-up-ritual-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up-ritual
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/wrap-up-ritual
Command: npx skills add https://github.com/Resgrid/Core --skill wrap-up-ritual-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents critical context from being lost when a session ends by capturing what was completed, what remains pending, and what was learned, then writing a handoff note for the next person or future session.

Core Features & Use Cases

  • Three-part wrap-up capture (DONE / PENDING / LEARNED): Ensures every session ending produces actionable continuity with no missing sections.
  • Single always-current handoff file: Overwrites .claude/handoff.md so the latest state is always available.
  • Learning-to-memory flow: Promotes reusable insights into MEMORY.md (via the self-correction loop) while still reflecting them in the handoff for immediate continuity.
  • Use cases: Software development work, exploratory research sessions, iterative refactors, and multi-task troubleshooting where handoffs across time or people are common.

Quick Start

When you say “wrap up” or “let’s stop here,” ask me to write the handoff note to .claude/handoff.md from your session’s completed work, pending tasks, and learnings.

Frequently Asked Questions about wrap-up-ritual

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

FAQPage Schema
How do I create handoff notes for a development session to prevent context loss?

Session handoff notes prevent context loss by capturing completed work, pending tasks, and learned insights into a structured summary file. This ensures the next developer or future session has immediate continuity without needing prior conversation history.

What is the best way to track pending tasks and completed work when stopping a coding session?

The best way to track session progress is using a three-part wrap-up capture: DONE, PENDING, and LEARNED. This structure ensures every session ending produces actionable continuity with no missing sections before writing to a handoff file.

How do I save reusable engineering insights from a session into long-term memory?

You save reusable insights by promoting durable learnings into a long-term memory file. This learning-to-memory flow ensures reusable knowledge is separated from immediate session context and made available for downstream feedback loops.

Does session wrap-up work for exploratory research and multi-task troubleshooting?

Session wrap-up works for exploratory research, iterative refactors, and multi-task troubleshooting. It applies to any development or research session that ends with context loss across time or different developers, ensuring no critical state is dropped.

How do I structure developer collaboration handoffs across different people?

Structure developer handoffs by overwriting a single always-current handoff file with a summary of completed work, pending tasks, and learned insights. This guarantees every collaborator reads the latest project state without parsing historical logs.