skills.rest
AgileSmagile
AgileSmagileCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

lets-wrap

Automate end-of-session wrap-up to capture knowledge and refresh agent memory.

4|Updated Apr 2, 2026
Search Tags:#checklist#agent#memory#session#knowledge-capture#wrap-up#board-hygiene
One-click install
npx skills add https://github.com/AgileSmagile/smagile-agentic-kanban-blueprint --skill lets-wrap-agilesmagile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lets-wrap
Source: https://github.com/AgileSmagile/smagile-agentic-kanban-blueprint/tree/main/skills/lets-wrap
Command: npx skills add https://github.com/AgileSmagile/smagile-agentic-kanban-blueprint --skill lets-wrap-agilesmagile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The wrap-up checklist ensures end-of-session discipline by guiding the agent to capture knowledge, maintain board hygiene, and update memory before signing off.

Core Features & Use Cases

  • Enforces a consistent end-of-session procedure across knowledge capture, board hygiene, and memory updates.
  • Surfaces actionable signals such as uncommitted changes, stale branches, and missing links to preserve context between sessions.
  • Use case: after finishing a project sprint, run the wrap-up to lock in decisions, tidy the board, and refresh memory for the next session.

Quick Start

End the current session and trigger the wrap-up checklist.

Frequently Asked Questions about lets-wrap

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

FAQPage Schema
How do I automate end-of-session wrap-up for a multi-card workflow?▼

You can automate end-of-session wrap-up by triggering a checklist that enforces memory updates, surfaces uncommitted changes, and maintains board hygiene across multi-card workflows.

What is board hygiene and why does it matter for agent memory?▼

Board hygiene maintains accurate, clutter-free project boards by surfacing stale branches and missing links, ensuring agent memory stays aligned with actual session decisions and uncommitted changes.

How do I capture knowledge and lock in decisions after finishing a project sprint?▼

To capture knowledge after a sprint, run a wrap-up checklist that surfaces actionable signals like uncommitted changes, updates memory, and tidies the board to lock in decisions for the next session.

Does the wrap-up checklist work across multi-card workflows without dependencies?▼

Yes, the wrap-up checklist applies across multi-card workflows with no external dependencies, using frontmatter-driven metadata to enforce consistent knowledge preservation and board hygiene between sessions.

What is the best way to surface uncommitted changes and stale branches before signing off?▼

The best way to surface uncommitted changes and stale branches is applying a wrap-up checklist that enforces surface checks, memory updates, and board tidying for consistent knowledge preservation.

Related Skills

Explore More Content & Communication Skills→
Jerry-Z07Jerry-Z07
21

start

Initialize AI development sessions by loading workflow guides, git status, and project guidelines.

Community
Intermediate
YurainSoonYurainSoon

session-end

Save current project state to PROJECT_STATE.md before ending a session.

Community
Basic
product-on-purposeproduct-on-purpose
527

iterate-refinement-notes

Capture backlog refinement outcomes into structured notes with frontmatter metadata.

Official
Basic
thomasholknielsenthomasholknielsen
2

claude-tweaks:wrap-up

Automate post-review reflections, artifact cleanup, and knowledge routing.

Community
Advanced