wrap

Update Obsidian vault files to record session outcomes and refresh context.

89|13|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/jdpolasky/ai-chief-of-staff --skill wrap-jdpolasky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap
Source: https://github.com/jdpolasky/ai-chief-of-staff/tree/main/.claude/skills/wrap
Command: npx skills add https://github.com/jdpolasky/ai-chief-of-staff --skill wrap-jdpolasky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you end each session without losing track of what was accomplished, what changed, and what still needs attention, by automatically updating the vault files that power the next briefing.

Core Features & Use Cases

  • Command Center freshness: Updates the **Last updated:** timestamp in Command Center so progress tracking stays current.
  • Task lifecycle capture: Moves all checked tasks from the four quadrants in To-Do.md into the ## Done section with appropriate date prefixing.
  • Session continuity: Appends a dated entry to _system/Session Log.md, overwrites _system/hot.md with low-fidelity “where things stand,” and updates _system/last_session.md with the new session number and recap.
  • Memory firing audit: Records which .claude/memory/ items actually influenced responses during the session.
  • Next-session readiness: Reflects wins and keeps session_context.md trimmed to the last 7 days so the next /start begins with relevant context.
  • Use case: After you finish working through today’s tasks in your Obsidian vault, run this to ensure your system is immediately ready for the next morning briefing.

Quick Start

Run the wrap skill at the end of your session to update Command Center, log what shipped, move checked tasks to Done, and refresh your session memory.

Frequently Asked Questions about wrap

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

FAQPage Schema
How do I automate task management and session logging in Obsidian at the end of a work day?

Automating session logging in Obsidian requires persisting shipped outcomes, moving checked tasks to a Done section, and refreshing context files. This ensures your vault records session numbers and memory continuity reliably for the next morning briefing.

What is the best way to update Obsidian vault files for workflow automation and next-session readiness?

Updating vault files for next-session readiness involves deterministic file edits to overwrite hot-context, append session logs, and trim context to the last 7 days. This workflow automation keeps your Command Center freshness and memory continuity current.

Can I move checked tasks from To-Do quadrants to a Done section automatically in Obsidian?

Yes, you can automatically move checked tasks from To-Do quadrants to a Done section. The process applies date prefixing during task lifecycle capture to ensure completed items are archived correctly within your Obsidian vault.

Does session wrap workflow automation require manual updates to the Command Center timestamp?

No, session wrap workflow automation automatically updates the Last updated timestamp in Command Center. This deterministic file edit ensures progress tracking stays current without manual intervention.

How does memory firing audit work for Obsidian workflow automation?

Memory firing audit records which memory items actually influenced responses during the session. It logs these specific memory continuity triggers to provide an accurate track record of active context within your vault.

When do I need to trim session context to maintain productivity in Obsidian?

You need to trim session context at the end of each work session to maintain productivity. Reflecting wins and keeping context trimmed to the last 7 days ensures the next session starts with only relevant, up-to-date information.