conclude

Generate a session log and update STATUS.md at session end.

4|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/gyoung55/cowork-session-skills --skill conclude
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conclude
Source: https://github.com/gyoung55/cowork-session-skills/tree/main/conclude
Command: npx skills add https://github.com/gyoung55/cowork-session-skills --skill conclude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures end-of-session context preservation by capturing a complete audit trail, writing a session log, updating state files, and preparing data for the next session.

Core Features & Use Cases

  • Session audit: automatically lists files created/modified and records open threads and decisions to keep context intact across sessions.
  • Session log generation: writes a machine-readable and human-friendly log at session-logs/YYYY-MM-DD-session-log.md with structured metadata.
  • State updates & hygiene: updates STATUS.md and performs workspace hygiene checks to keep the project clean and ready for the next session.
  • Cross-project handoffs: flags data or decisions that affect other projects and supports handoff workflows.

Quick Start

End a session by running /conclude to generate a session log and update project state.

Frequently Asked Questions about conclude

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

FAQPage Schema
How do I preserve context and log session status at the end of a workflow?▼

To preserve context across work sessions, run an end-of-session wrap-up that audits modified files, records decisions, and logs open threads. This generates a dated session log and updates project state files to maintain continuity for the next workflow.

What's the best way to generate a session log and update STATUS.md for project handoffs?▼

The best way to generate a session log and update STATUS.md is to apply a deterministic workflow at session end. This process writes a structured log to a dated session-logs file and updates STATUS.md to prepare the project for cross-project handoffs.

How does an end-of-session audit trail work for tracking modified files and decisions?▼

An end-of-session audit trail works by automatically listing files created or modified during the workflow and recording open threads alongside key decisions. This captured data is compiled into a structured log to preserve context and maintain project state.

Can I use a session log to flag cross-project handoffs and open threads?▼

Yes, you can use a session log to flag cross-project handoffs and open threads. The wrap-up process identifies data or decisions that affect other projects and records them, supporting seamless handoff workflows between different project contexts.

Do I need a deterministic workflow to maintain project state and session logs?▼

Yes, you need a deterministic workflow to reliably maintain project state and session logs. The process requires this structured approach to consistently write the final session log to a dated markdown file and update STATUS.md as part of workspace hygiene.

What are the limitations of manually tracking session context without an audit log?▼

Without an automated audit log, manually tracking session context risks losing track of modified files, open threads, and cross-project handoffs. A structured end-of-session process overcomes this by systematically capturing decisions and updating state files to ensure context preservation.