session-close

Name: session-close
Availability: InStock
Author: AMDResearch

Automates end-of-session orchestration across workflow, PM, and state artifacts with commit and capture procedures.

3|3|Updated Aug 19, 2024

Search Tags:#workflow #documentation #commit #handoff #end-of-session #session-close

Ready to run

npx skills add https://github.com/AMDResearch/dh_comms --skill session-close-amdresearch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: session-close
Source: https://github.com/AMDResearch/dh_comms/tree/main/.agents/skills/session-close
Command: npx skills add https://github.com/AMDResearch/dh_comms --skill session-close-amdresearch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-of-session workflow to ensure all required updates and artifacts are completed consistently, reducing manual drift and missed steps at project closure.

Core Features & Use Cases

Update workflow documents (run-log, handoff, and relevant dossier) with current status, next steps, and blockers.
Refresh Project Memory (pm-current-state, pm-decisions, pm-glossary, pm-index) to reflect decisions and new terminology from the session.
Sync state files (current-focus, active-workflows) to accurately reflect the project's status.
Commit changes in logical groups with descriptive messages to maintain traceability.
Run session-capture to normalize the session record and apply review cadence as needed.
Deliver a user-facing summary and ensure .agents/state/session-active.md is removed to signal closure.

Quick Start

Run /session-close to execute the full end-of-session workflow.

Frequently Asked Questions about session-close

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

FAQPage Schema

How do I automate end-of-session workflow updates and project handoff?▼

Automate end-of-session updates by coordinating changes across workflow, PM, and state artifacts to ensure a clean handoff. This process updates run-logs, dossiers, and project memory while enforcing safe commit practices for consistent project closure.

What is the best way to commit workflow documentation and project state files together at session end?▼

Commit workflow documentation and state files at session end by grouping changes logically with descriptive messages. This maintains traceability and ensures all relevant project memory and state markers are captured safely before closure.

How does session-capture normalize project memory and active workflow state?▼

Session-capture normalizes project memory by refreshing pm-current-state, pm-decisions, and pm-glossary to reflect new terminology and decisions. It also syncs active-workflows and current-focus state files to accurately represent the project's status.

Can I use automated session-capture for multi-artifact project management workflows?▼

Automated session-capture is designed for project-management workflows where multiple artifacts must be updated, committed, and captured. It coordinates updates across all relevant files and removes the session-active marker to signal proper closure.

Why do I need to remove the session-active marker during project handoff?▼

Removing the session-active marker signals closure and prevents stale state conflicts. It ensures the system recognizes the previous work session has ended after all workflow documents, project memory, and state files are committed and normalized.

When should I avoid automating end-of-session workflow orchestration?▼

Avoid automating end-of-session orchestration if your project lacks structured workflow documents, project memory artifacts, or state files. The process requires defined PM artifacts like run-logs, dossiers, and current-focus markers to execute proper commit and capture procedures.