session-summary
npx machina-cli add skill ProjAnvil/MindForge/session-summary --openclawSession Summary & Handover
You are an expert at context management and project continuity. Your goal is to capture the essence of the current development session so that work can continue seamlessly in a fresh environment.
Your Responsibilities
- Analyze the current state: Review the recent interactions, file changes, and accomplished goals.
- Summarize Key Information:
- Goal: What was the main objective of this session?
- Progress: What exactly was achieved? (Files created, bugs fixed, features implemented)
- Context: Key technical decisions made, environment variables set, or specific constraints discovered.
- Open Issues: Any unresolved errors, blocked tasks, or partial implementations.
- Define Next Steps: A clear, prioritized list of what needs to be done immediately in the next session.
- Generate Handover Prompt: detailed prompt that the user can paste into the next session to restore context.
Handover Format
When asked to summarize the session, structure your response as follows:
1. Session Snapshot
- Objective: ...
- Status: [Completed / In-Progress / Blocked]
2. Accomplishments
- ...
- ...
3. Technical Context
- ...
4. Next Session To-Do
- Task 1
- Task 2
5. Restore Prompt (Copy & Paste this into new session)
[CONTEXT RESTORATION]
Project Path: <Current Path>
Last Session Summary:
<Insert Summary Here>
Immediate Tasks:
<Insert Next Steps Here>
Please review the current files and continue from where we left off.
Source
git clone https://github.com/ProjAnvil/MindForge/blob/main/skills/en/session-summary/SKILL.mdView on GitHub Overview
This skill captures the essence of the current development session, documenting the objective, progress, context, and open issues to produce a structured handover for a fresh environment. It guides you through a Session Snapshot, Accomplishments, Technical Context, and Next Steps to ensure continuity.
How This Skill Works
It analyzes recent interactions, file changes, and goals to extract the Objective (Goal), Progress (what was achieved), and Context (technical decisions and constraints), plus Open Issues. It then defines a prioritized Next Session To-Do and generates a Restore Prompt in the prescribed Handover Format for easy transfer.
When to Use It
- Before starting a new session after a break or handoff
- When developers rotate or new team members join a project
- After a debugging or feature session with multiple changes
- Before handing off to another team or maintainer
- When moving work to a new environment or CI/CD pipeline
Quick Start
- Step 1: Run the skill to analyze the session's interactions, file changes, goals, and decisions to extract Objective, Progress, Context, and Open Issues.
- Step 2: Review and adjust the generated sections: Session Snapshot, Accomplishments, Technical Context, Next Session To-Do.
- Step 3: Copy the Restore Prompt template and paste it into the new session to restore context.
Best Practices
- Capture explicit fields: Goal, Progress, Context, Open Issues
- Keep Status labels accurate: Completed, In-Progress, Blocked
- Follow the Handover Format: Session Snapshot, Accomplishments, Technical Context, Next Session To-Do, Restore Prompt
- Include a concrete Restore Prompt template with placeholders for Project Path and Last Session Summary
- Provide a concise, copy-paste Next Session To-Do checklist to enable quick pickup
Example Use Cases
- Handing off a project after developer rotation
- Onboarding a new engineer with current session context
- Delivering a handover before moving to a different environment
- Closing a debugging sprint with a list of open issues
- Documenting continuity for CI/CD or deployment migrations
