wrap

Archive completed tasks and update YAML statuses in BACKLOG.md.

42|9|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/lsnackerman/raw-clauding-skills --skill wrap-lsnackerman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/lsnackerman/raw-clauding-skills/tree/main/wrap
Command: npx skills add https://github.com/lsnackerman/raw-clauding-skills --skill wrap-lsnackerman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End sessions with a clean, intentional close that preserves work and ensures continuity for future sessions.

Core Features & Use Cases

  • Update task docs with status changes, next steps, and observations to keep a living record of work.
  • Close out finished work by archiving tasks and summarizing learnings for the next session.
  • Create a clear handoff by recording energy, decisions, and a pointer to the next steps in BACKLOG.md.

Quick Start

Run the wrap at the end of your session to preserve the work and create a clean handoff.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I end a work session while preserving context for the next one?

To end a work session while preserving context, update task documentation with status changes, archive completed items to a done folder, and record reflections in BACKLOG.md for a clean handoff.

What is the best way to create a task handoff for a future session?

The best way to create a task handoff is to record your energy, decisions, and next steps in BACKLOG.md, ensuring you update YAML status fields and move finished tasks to an archive directory.

How do I archive completed tasks and update their YAML status to done?

You archive completed tasks by moving finished items to a designated done directory and enforcing YAML status updates to done, which keeps your task management files clean and accurate.

Can I use this approach to manage task documentation and backlog items together?

Yes, you can manage task documentation and backlog items together by updating task docs with observations and delivering a final handoff pointer directly to BACKLOG.md to ensure project continuity.

Does ending sessions gracefully require manually moving finished task files?

Ending sessions gracefully automates the process of moving finished task files to a done folder, enforcing YAML status updates to done, and adding session reflections without manual file shuffling.

When do I need to record observations and next steps for task continuity?

You need to record observations and next steps at the end of every work session, adding them to your task docs and BACKLOG.md to ensure a clean handoff and continuous workflow.